Home · Setup · Claude.ai and Claude Desktop connectors
One double-entry ledger derived from the books you already keep, proved to zero to the minor unit, with every line naming the document it came from. It reads six books this collection already keeps, all read-only: the invoice ledger, the credit notes and purchase orders, the deposits, the expense ledger, the bank import and the fixed asset register. For a period in one currency it derives a debit and a credit for every movement in them. Revenue and VAT output come off the invoices, receivables and the payments that clear them, deposits held as the liability they actually are, expenses by category with the VAT taken OUT of the gross rather than added on top of it, fixed assets as they enter service, and depreciation charged by month. The bank import posts nothing at all, which is the decision the whole ledger rests on: a bank line and a payment record are not two transactions, they are one transaction seen twice, so cash is posted from the documents, which are the only rows that carry a second leg, and each bank row is matched to a posted cash movement of the same amount, the same direction and a date within three days, written onto the line as evidence. What is left unmatched is the output that matters, because a bank debit with no expense behind it is a payment nobody entered. Nothing is ever balanced with a plug: an entry whose own legs do not add up is posted exactly as the document states it and the difference is raised by name, with the entry, the source server and the source document behind every unit of it, because a trial balance can only find a broken document if it is allowed to come out non-zero. Currencies are never added together, a purchase order stays a memo and is never posted, a deposit applied to an invoice moves the liability rather than cash, and the ledger opens at nothing, since an opening figure nobody can walk back to a document is the first invented number in a set of books. Every line carries the server, the document id and the ISO date it came from, and the bytes and mtimes of all six sibling stores are unchanged across all six tools.
The six books this server derives from live in the hosted store behind the token, so a ledger built here reads the invoices, credit notes, purchase orders, deposits, expenses, bank imports and assets raised through those connectors on that same token, and nothing else. That is the shape this client can actually hold: no six local data directories to point at, no paths to type, and a trial balance whose figures follow the key rather than the machine. There is no network call inside the server itself, so the double-entry arithmetic and the bank matching are the same here as on a laptop, down to the minor unit, and the three free periods a calendar month are counted against the token. ledger_export_csv returns the CSV as text either way, since it writes no file on any route.
| You say | Tool |
|---|---|
| Build the double-entry ledger for June and tell me whether the trial balance comes to zero. | ledger_build |
| Show me every ledger line that hits receivables, with the invoice each one came from. | ledger_lines |
| Close June: what does the month leave unposted or inconsistent? | month_close |
Posting the bank import alongside the documents, which is the obvious way to build a cash book and the way most spreadsheets do it, double-counts almost all of the cash and the trial balance still comes to zero. Measured on this server's worked month: four of the five bank rows are the same money as a document already posted, 1,375,300 of 1,380,300 minor units of cash movement, 99.6 percent. Posting them as well moves the cash balance from -10,543.00 to -21,111.00 EUR, and nothing flags it, because every duplicated receipt arrives with its own contra, every individual line is plausible and the only symptom is one account off by nearly a factor of two in a direction nobody audits. What is left after matching is 7,500 minor units, one unexplained withdrawal. That 0.4 percent is the entire reason to import a statement at all, and it is exactly what a duplicate-heavy ledger buries.
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/cash-book/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 Cash Book 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: trial_balance and ledger_lines are free and unlimited on every tier. Whether the books add up is the question this server exists for, and a free tier that hides the answer is a demo rather than a tool, so neither the check nor the evidence behind it is ever metered. The cap is on the PERIOD instead: three distinct periods a calendar month, keyed by from, to and currency, so rebuilding a period already in the register is free forever on every tier and the meter only ever moves when you ask a genuinely new question. 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 Cash Book for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Cash Book produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Cash Book 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