Home · Setup · Claude.ai and Claude Desktop connectors
The one document that answers what a client actually owes you, aged as at any date you name, with the chaser drafted. It reads the three books this collection already keeps, the invoice ledger, the credit notes and the deposits, and turns them into a statement of account for a period: the balance carried at the start, every invoice issued, every payment received, every credit note given, the deposits applied broken out of the receipts rather than added on top of them, and the balance at the end. The movements come back in date order and the opening balance plus their sum is the closing balance, so the document reconciles line by line rather than only at the bottom. statement_aging splits what is still open into 0-30, 31-60, 61-90 and over 90 days past the due date AS AT the date you ask for, which means an invoice issued after that date is not on the books, a payment made after it has not happened, and a credit note issued after it has not been given. Due today is not overdue: day zero sits in a not-yet-due line reported beside the four buckets rather than hidden inside them. On the invoice the paid_minor field is the authority and the payment rows are only the attribution, so money that a deposit application put on an invoice without writing a payment row still appears, and when the two books disagree the difference is reported by name rather than scaled away. It writes into no book it reports on: the bytes and the mtimes of the sibling stores are unchanged across all six tools, and the only file it owns is a register of the statements it built. Nothing here invents a late fee, an interest rate or a legal cost, and a dunning letter escalates in tone and never in figures.
The three books this server reads live in the hosted store behind the token, so a statement built here sees the invoices, credit notes and deposits raised through the invoice, billing-docs and deposits connectors on that same token, and nothing else. That is the shape this client can actually hold: no local ledger to point at, no path to type, and a statement whose figures follow the key rather than the machine. There is no network call inside the server itself, so the aging arithmetic is the same here as on a laptop, down to the minor unit, and the five free statements a calendar month are counted against the token.
| You say | Tool |
|---|---|
| Send Acme Ltd a statement of account for June. What is the closing balance, and does it reconcile from the opening balance and the movements? | statement_build |
| Who owes me money right now, aged into 0-30, 31-60, 61-90 and over 90 days, per currency? | statement_aging |
| What was outstanding on 10 June, and how much of that was already overdue on that date? | statement_aging |
Aging a past date with today's payment figures does not go slightly wrong, it goes silently empty. Measured on this server's worked month at 2026-06-10: the as-at rule reports 2,500.00 outstanding of which 500.00 is 31 days late, while the ordinary rule almost every aging report is written as, subtract paid_minor and bucket by the due date, reports 1,700.00 outstanding and ZERO overdue, because a payment that arrived on 12 June has already been subtracted on the 10th. A third of the balance and all of the overdue disappear, the buckets still add up, and the answer cannot be reproduced next month because the input keeps moving. The dated subtraction is the step nobody writes a test for and the only one that decides who gets chased. A second measured figure from the same month: reconstructing receipts from the invoice payments[] rows alone would have lost 300.00 of 900.00 of cash, because deposit_apply raises paid_minor and writes no payment row, so paid_minor is treated as the authority and the rows only as the attribution.
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/https://mcp.zovo.one/mcp/statement-of-account/t/<token>. That URL works with no headers: the token is in the path, not in an Authorization field this form does not have.
Idle anonymous tokens are swept after 30 days. Since this route has no filesystem, a file MCP Statement of Account 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.
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: statement_aging is free and unlimited on every tier, for one client or for all of them: who owes me money is the question this server exists for, and a free tier that hides it is a demo rather than a tool. The meter is on the document that actually goes to a client, five distinct statements a calendar month, counted by client, period and currency, so rebuilding one already in the register is free forever. Plain-text statements and dunning letters at level 1 and level 2 are free. Pro is $19 once, verified offline, and binds to the token after checkout.
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.
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.
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 Statement of Account for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Statement of Account produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Statement of Account 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