Home · Setup · Claude.ai and Claude Desktop connectors
Credit notes and purchase orders written against the invoices the invoice server already holds, with the VAT unwound at the rate you charged. It credits an invoice in full, by a gross amount or by named lines and quantities, storing every money field negative in minor units so a period's documents sum to the net of what was billed, and it refuses to give back more than the invoice's remaining creditable amount. It also raises purchase orders to suppliers with line items, VAT, currency and an expected delivery date, receives them in full or in part, and reports credited and on-order totals per currency alongside deliveries past their date.
Credit notes and purchase orders are written against the same invoice store /mcp/invoice serves for this token, so an invoice raised on the hosted invoice endpoint can be credited here without a file changing hands; both PDFs and both text exports come back as one-hour download links rather than paths.
| You say | Tool |
|---|---|
| Credit invoice INV-2026-0001 in full, the client sent the work back. | credit_note_create |
| Raise a purchase order to Nordic Print for 500 brochures at 1.20 each, due the 20th. | purchase_order_create |
| Which purchase orders are past their delivery date? | billing_docs_report |
Crediting ten percent of a mixed-VAT invoice at a single rate and splitting it across the invoice's own rates give the same gross, EUR 177.00, and VAT lines that differ by EUR 6.10, 22.6 percent. The client's document and the payment are identical either way, so nothing downstream ever surfaces the error; only the VAT return does. The split is done at the point the document is written.
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/billing-docs/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 Billing Docs 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: 5 documents a calendar month, credit notes and purchase orders together, counted by issue date. Both text exports are never metered, and full, partial and per-line credit notes, VAT, multiple currencies and receiving orders are all on the free tier. 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 Billing Docs for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Billing Docs produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Billing Docs 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