MCP for affiliates

If you are an approved member of the referral program, you can connect an AI assistant (Claude Code, Claude Desktop, Cursor) to your own program account. The assistant reads your figures, statements and ledger, downloads the support document and can prepare a statement's invoice. It never submits an invoice without your confirmation.

The server is https://www.notificado.co/mcp/afiliados. It is separate from the firms' server (/mcp): an affiliate token opens nothing of a firm, and a firm token opens nothing here.

What the assistant sees

Only your affiliate account. The token acts as you: there is no way to ask for another affiliate's account, nor for any firm's cases, notifications or evidence, your own firm's included.

1. Create a token

1. Sign in and open /afiliados. The Agent access (MCP and API) section shows once your membership is approved.
2. Give it a name that says where you will use it (for example, "Claude Desktop, laptop").
3. Choose the scopes. Grant only the ones you need.
4. Press Create token. The token is shown once, with a button to copy it. We keep only its fingerprint: if you lose it, revoke it and create another.

The same section lists each token with when it was created, its last use and its expiry, and you revoke it whenever you want. A revoked token stops working on the next call.

2. Connect your client

Claude Code, with one command:

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

Claude Desktop, through the mcp-remote bridge (needs Node.js), in its configuration file:

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

Cursor, by URL and header, in mcp.json:

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

Replace <token> with the one you copied. The affiliate server offers no OAuth sign-in: it is always a token. To test the connection, ask the assistant to call whoami({}) and then list_resources({}).

How the assistant works

As on the firms' server, the assistant sees five tools: list_resources, describe_resource, manage_resource, docs and whoami. Your account's actions sit behind three resources and run with manage_resource:

manage_resource({ resource: "account", action: "myAffiliateSummary", params: {} })

Each token sees only the actions its scopes open. The server itself hands out three recipes through the docs tool: reading the dashboard (docs://affiliate/read-my-affiliate-dashboard), submitting a statement's invoice (docs://affiliate/file-a-statement-invoice) and checking the verification (docs://affiliate/check-my-kyc-status).

Scopes

The invoice waits for your confirmation

When an assistant submits an invoice with affiliate:invoices, Notificado does not take it yet: it keeps it as pending and shows it on /afiliados, under Invoices sent by an agent, with the statement, the channel it came by and each file's SHA-256 fingerprint. The assistant gets awaiting_confirmation and a link that opens that invoice on /afiliados. You have 7 days to confirm it; after that it expires unsubmitted.

• Confirm: the invoice is submitted as if you had uploaded it, and checked against what the statement asks for.
• Reject: the invoice is discarded and the statement keeps waiting for one.

An agent cannot confirm its own invoice. If the invoice does not match the statement (NIT, amounts, date), confirming it refuses it with the same reasons you would see uploading it yourself. If the files change after the agent sent them, the confirmation is refused and the agent must send it again.

What only you do

These have no MCP tool and no API operation, under any scope:

• Applying to the program and accepting the terms.
• The identity and tax verification (document, RUT, regime).
• The payout account: where your commissions are transferred.
• Confirming or rejecting an invoice sent by an agent.
• Creating and revoking affiliate tokens.

The same account over HTTP

Every read and the invoice are also on the affiliate API, https://www.notificado.co/v1/afiliados, with the same token and the same scopes. See API for affiliates.

Limits

The affiliate server shares the rest of the MCP's rate rules: past the limit, the answer is HTTP 429 with retry-after, the seconds to wait. See Limits.