Home · Setup · Claude.ai and Claude Desktop connectors
Receipts, mileage and expenses that turn into invoice lines. It logs an expense with its own currency and VAT split, records the receipt by path and sha256, and emits invoice lines that are not taxed twice.
receipt_attach still wants a path, and the connector has no local filesystem, so the practical route here is amounts and a description rather than a stored receipt file.
| You say | Tool |
|---|---|
| I paid 61.50 EUR at Media Markt for a USB hub, Acme project, billable. | expense_add |
| What did I spend this month, by category? | expense_summary |
| Give me the invoice lines to rebill Acme this month with 10% markup. | expense_to_invoice |
The EUR 61.50 receipt above stored as amount_minor 6150, vat_rate 23, and rebilled at a net unit_price of 50.00, so the invoice did not tax it twice.
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/expense-tracker/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 Expense Tracker 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: unlimited logging, 30 days of history, 3 projects, 5 rules, 200 CSV rows. 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 Expense Tracker for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Expense Tracker produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Expense Tracker 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