Skip to content

Notificado, from your AI assistant

An MCP server with the same permissions as your account. Your assistant registers cases, uploads documents, prepares the notification and reads the evidence; you confirm the send.

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 your MCP client

Signing in leaves nothing to copy. With a token, replace <token> with the one you issued under Account → API, and never paste it into a chat or a shared file.

Claude Code: sign in (recommended)
claude mcp add --transport http notificado https://www.notificado.co/mcp

Recommended: Claude Code with sign-in, no token. The first time you use it, Claude Code opens your browser; sign in as the firm's owner or a lawyer and allow the connection. It stays active while you use it and renews itself; it closes after 60 days without use.

Claude Code: personal token
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.

Developer tools that accept a remote MCP server connect too, among them Claude Code, Cursor, Gemini CLI, ZCode, Kimi Code, VS Code. Each tool's documentation says where to add the server address.

What you can automate

Each tool belongs to one scope, and a token sees only the tools of the scopes it was issued with.

  • 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.

  • billing:read

    Credits and invoices

    Read the firm’s credit statement and electronic invoices, and download an invoice.

  • activity:read

    Firm activity

    Read who drafted, swore, sent, confirmed or downloaded, and every member and token change.

  • webhooks:manage

    Firm webhooks

    Register, test and manage the endpoints that receive every send, delivery, bounce, acknowledgement and constancia, signed.

Authentication

Issue a token under Account → API. It is shown once, and we store only its hash.

  • Pick its scopes and lifetime: 30, 60, 90, 180 or 365 days, a specific date, or no expiry. Revoke the tokens you no longer use under Account → API.
  • The token acts for the person who issued it, with their current role in the firm. If the role changes, the token follows on the next call.
  • Revoke it at any time from the same page.
  • Limits: 120 reads and 20 writes a minute per person.

An assistant prepares everything, but never sends on its own

  1. The assistant prepares

    It registers the case, uploads the documents and creates the draft. Nothing is sent and no credit is used.

  2. You add the recipients

    Adding a recipient is your sworn statement about where the address came from (art. 8, inciso 2). Only you make it, in the panel.

  3. The assistant requests the send

    It gets a confirmation link, valid for 24 hours, and hands it to you.

  4. You confirm

    In the panel, signed in. Only then is the message frozen, timestamped and sent.

Step-by-step guides for your assistant

Written for agents, indexed by goal. Your assistant reads them with the docs tool; they are also published in the documentation.

The full documentation

Tools, scopes, errors and the API reference, generated from the same code that answers the calls.