Technical reference

MCP server

Notificado's MCP server is at https://www.notificado.co/mcp. A connected assistant prepares cases and drafts, checks deliveries and downloads evidence; it never sends on its own.

Your AI assistant follows the art. 8 recipe over MCP: it finds the case, uploads the auto and drafts the notification. You add the recipients and confirm the send.

Connect a client

Replace <token> with the one you issued under Account → API. Never paste it into a chat or a shared file.

You need an agent token, issued under Account → API. Authentication guide

Claude Code

claude mcp add --transport http notificado https://www.notificado.co/mcp --header "Authorization: Bearer <token>"

Claude Desktop

{
  "mcpServers": {
    "notificado": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.notificado.co/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <token>"
      }
    }
  }
}

Claude Desktop reaches remote servers through mcp-remote, which needs Node.js. Add this to claude_desktop_config.json.

Cursor

{
  "mcpServers": {
    "notificado": {
      "url": "https://www.notificado.co/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

In Cursor, add it to ~/.cursor/mcp.json or to the project's .cursor/mcp.json.

Other clients: if yours can connect to a remote HTTP MCP server sending a custom Authorization header, it works with the same address and token; consult your client's docs. If it only supports other sign-in methods, it cannot connect yet.

To test the connection, ask the assistant to call whoami({}) and then docs({}).

Tools

The 23 tools a token can ever be shown. Each token sees only its scopes' tools, plus docs and whoami. Descriptions are in English: they are what the assistant reads.

Tools
Tool	Scope	What it does
`caseList`	`cases:read`	The caller's firm's cases (procesos), newest first: id, 23-digit radicado, juzgado, ciudad, especialidad, clase de proceso and cliente.
`caseDetail`	`cases:read`	One case of the caller's firm by caseId (from caseList): 23-digit radicado, juzgado and its email, ciudad, especialidad, clase de proceso, cliente, its parties (role demandante \| demandado \| apoderado \| otro, name, idNumber) and `locked` — true once a notification of it left draft, after which the case can no longer be edited.
`createCase`	`cases:write`	Create a case (proceso) in the caller's firm.
`updateCase`	`cases:write`	Correct a case of the caller's firm: pass caseId and only the fields to change (radicado — 23 digits, dashes/spaces allowed —, juzgado, juzgadoEmail, ciudad, especialidad, claseProceso, cliente).
`addParty`	`cases:write`	Add a party to a case of the caller's firm: caseId, role demandante \| demandado \| apoderado \| otro, the name as written in the demanda, and idNumber (cédula or NIT with its check digit) when known.
`requestUpload`	`cases:write`	Step 1 of 2 of an upload: get a signed, single-use PUT grant for ONE file.
`confirmUpload`	`cases:write`	Step 2 of 2 of an upload, after the PUT to requestUpload's url succeeded: pass the same key, kind, filename and contentType.
`notificationList`	`notifications:read`	List the org’s notifications, newest first: id, case, status (draft \| freezing \| frozen \| sending \| sent \| failed), subject, the frozen .eml SHA-256 and UTC timestamps.
`notificationDetail`	`notifications:read`	One notification by id: status, recipients with delivery status and how each address was obtained, attachments with SHA-256, and the evidence timeline (message.frozen, transport.sent, mail.delivery, bounces, downloads, acknowledgements) in chain order with UTC times.
`creditsBalance`	`notifications:read`	Credits balance of the caller's org: `balance` is how many recipients can still be notified (one credit per recipient, consumed on send), and `nextExpiryAt`/`nextExpiryCredits` say when the soonest batch of credits expires (UTC).
`verifyConstancia`	`notifications:read`	Public check of a Notificado constancia: pass the verification code printed under its QR ("code") or the SHA-256 of the PDF file ("pdfSha256").
`memorialReadiness`	`notifications:read`	Whether a memorial can be generated now for one notification in your organization.
`notificationMemorials`	`notifications:read`	The memorials generated for one notification in your organization, newest first: id, createdAt, and the SHA-256 and size of the DOCX and the PDF, plus factsSha256 (the hash of the facts the memorial cites).
`createNotification`	`notifications:write`	Create a DRAFT art.
`updateDraft`	`notifications:write`	Rewrite a DRAFT art.
`attachDocument`	`notifications:write`	Attach an already-uploaded document (documentId) to a DRAFT notification, as kind auto_admisorio \| demanda \| anexo \| subsanacion \| providencia \| otro.
`sendNotification`	`notifications:write`	REQUEST the send of a draft notification — REQUIRES HUMAN CONFIRMATION.
`createMemorial`	`notifications:write`	Generates the memorial (DOCX + PDF draft, in Spanish) that informs the juzgado that personal notification under art.
`downloadEvidence`	`evidence:read`	Returns the bytes (base64, with filename, content type and SHA-256) of the signed constancia PDF (kind "constancia") or the offline-verifiable evidence zip (kind "zip") of one notification in your organization; newest version unless "version" is given.
`downloadMemorial`	`evidence:read`	Returns the bytes (base64, with filename, content type and SHA-256) of one generated memorial in your organization, as "docx" (editable, for the lawyer to review and sign) or "pdf" (with the constancia verification QR).
`listDeadlines`	`deadlines:read`	The caller's firm's deadlines (términos) under Ley 2213 art.
`docs`	Always available	The recipes and guides for agents: the index, a search, or one whole document.
`whoami`	Always available	The firm (orgId), role, scopes and token prefix the assistant is calling with.

Scopes

Scopes
`cases:read`	Read cases List the firm's cases (procesos) and their parties.
`cases:write`	Register cases and upload documents Create and edit cases and parties; upload PDF, PNG or JPEG.
`notifications:read`	Follow notifications Each recipient's status, their evidence timeline, the credit balance and constancia verification.
`notifications:write`	Prepare notifications Create drafts, attach documents and request the send, which you confirm.
`evidence:read`	Download evidence The signed constancia and the evidence package. Every download is logged.
`deadlines:read`	Read deadlines Computed terms per recipient, on the Colombian court calendar.

No scope allows adding or removing recipients, confirming a send, buying credits, or entering the staff console.

Confirm before send

An assistant prepares everything, but never sends on its own

The assistant prepares. It registers the case, uploads the documents and creates the draft. Nothing is sent and no credit is used.
You add the recipients. Adding a recipient is your sworn statement about where the address came from (art. 8, para. 2). Only you make it, in the panel.
The assistant requests the send. It gets a confirmation link, valid for 24 hours, and hands it to you.
You confirm. In the panel, signed in. Only then is the message frozen, timestamped and sent.

Limits

120 reads and 20 writes a minute per person, across all their tokens. Over the limit the answer is HTTP 429 with retry-after. All limits

Recipes for agents

The same instructions the MCP server gives AI assistants through the docs tool. They are in English, because models follow them best that way.