Home · Setup · Claude.ai and Claude Desktop connectors

MCP Deposits in Claude.ai and Claude Desktop connectors

Security and retainer deposits held per client, applied to the invoices the invoice server already holds. It records a deposit when the money arrives, in minor units and in the currency it arrived in, then answers for it: what is held per client and per currency, since when, and what has already gone. Applying a deposit to an invoice writes the payment onto that invoice under both locks, adding to what was already paid rather than replacing it, and it can never pay out more than the deposit still holds or more than the invoice still owes. Refunds hand the money back without touching the invoice, and the statement is one client in one currency, as text or as an A4 PDF that matches the invoice and credit note beside it.

The deposit ledger and the invoices it pays down are the same store /mcp/invoice serves for this token, so applying a deposit here moves the balance on an invoice raised on the hosted invoice endpoint, with no file changing hands; the A4 statement comes back as a one-hour download link rather than a path, and the text statement, which is what most people actually send, needs no download at all.

What you get

You sayTool
Record a 500 euro security deposit from Nordic Print, received today.deposit_record
Apply 300 of that deposit to INV-2026-0001.deposit_apply
How much are we holding for Nordic Print, and since when?deposit_balance

deposit_apply ADDS to the invoice's amount paid rather than setting it. Measured through a real client on 2026-09-05: an invoice already carrying a EUR 200.00 bank transfer ended at paid_minor 50000 after a EUR 300.00 deposit was applied, reported as paid EUR 500.00 of EUR 1,230.00 with EUR 730.00 due. Writing this server against the same field is what surfaced that invoice_mark_paid was assigning rather than adding, which silently lost the earlier payment; the invoice server was fixed the same day and now adds too.

Connect it, no install

https://mcp.zovo.one/mcp/connect mints an anonymous token and prints a URL per server, including this one, shaped like https://mcp.zovo.one/mcp/deposits/t/<token>. That URL works with no headers: the token is in the path, not in an Authorization field this form does not have.

  1. Open https://mcp.zovo.one/mcp/connect and copy the URL printed for MCP Deposits.
  2. There is no config file here: the Add custom connector form asks for a name and a Remote MCP server URL, with an Advanced settings section for an optional OAuth Client ID and Client Secret.
  3. Paste the URL as the Remote MCP server URL. Leave the optional OAuth Client ID and Client Secret blank; this endpoint does not use them.
  4. Click Connect, then turn the connector on for a conversation from the + button, Connectors.

Idle anonymous tokens are swept after 30 days. Since this route has no filesystem, a file MCP Deposits generates comes back as a download link that expires after one hour. A Pro key can replace the token in the same URL and removes the free-tier limits.

Claude.ai and Claude Desktop connectors notes worth knowing first

On an individual Pro or Max plan you add the connector yourself from Customize, Connectors. On Team and Enterprise it is the other way round: only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, and members then connect to what the Owner added rather than pasting their own URL.

Free: 5 deposits recorded a calendar month, counted by received date. Applying to invoices, refunds, lists, balances and the text statement are unlimited on every tier: a cap that trapped a client's deposit would be a limit on their money rather than on yours. Pro is $19 once, verified offline, and binds to the token after checkout.

Questions

Does this need OAuth?

No. Add custom connector offers an Advanced settings section with an OAuth Client ID and Client Secret, but the connect-by-URL route does not use it. Leave both blank: the token in the URL path is what authenticates.

I am on a Team or Enterprise plan and cannot add a connector.

That is documented, not a bug: on Team and Enterprise, only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, Add, Custom, Web. After that, members connect to the URL the Owner added from Customize, Connectors.

Can I use my Pro key instead of the free anonymous token?

Yes. The token segment of the URL from /mcp/connect can be replaced with a Pro key, which removes the free-tier limits on MCP Deposits for that connector.

Why did a generated file come back as a link instead of opening?

The connector runs server-side with no filesystem of its own, so any file MCP Deposits produces is handed back as a download link that expires after one hour, rather than a path on disk.

Related

MCP Deposits in detail · How connect-by-URL works · Every server for Claude.ai and Claude Desktop connectors · All clients · Claude.ai and Claude Desktop connectors docs · Buy Pro