Home · Setup · Claude.ai and Claude Desktop connectors
Mileage log for deductible driving: trips, effective-dated rates, summaries and CSV export. You log each drive the moment it happens - the date, where from and to, the distance in miles or km, the purpose and the category (business, medical, moving, charitable, personal) - and it comes back with a TR-YYYY-NNNN id, a future date refused because the trip cannot have been driven yet. rate_set records what one mile or km is worth for one category in one jurisdiction from a date forward, an effective-dated series rather than one global number, and each trip earns the rate in force on the day it was driven, rounded half-up to the cent, with totals summed from the rounded per-trip amounts so the CSV reconciles line by line with the summary. Distances in miles and in km are kept apart and never added together; a trip whose unit differs from the rate's is converted first, 1 mile = 1.609344 km exactly. Trips with no applicable rate are listed with the reason, never silently dropped, and the export refuses while any non-personal trip in the window is unpriced, so an accountant never receives a log with silent gaps. No rate ships with the server and none of it is tax advice: the rates you set are your own figures to verify.
The log and the rate book live in the hosted store behind the token, so the twenty free trips a month and the TR-YYYY-NNNN numbers follow the key rather than the machine. There is no network call inside the server on any route, so the pricing is identical here and on a laptop, down to the cent: the rate in force on the trip's day, rounded half-up once per trip, and totals summed from those rounded amounts. mileage_export is Pro and its CSV comes back in the answer itself, because a hosted call has nowhere local to write it.
| You say | Tool |
|---|---|
| Set the US federal business rate at 0.70 a mile from 2026-01-01. | rate_set |
| Log yesterday: home office to the client site at 2 Mill Lane, 12.5 miles, the Kowalski site visit. | trip_add |
| Summarize this year's deductible mileage. | mileage_summary |
The contract suite asserts the arithmetic over real stdio: 12.5 miles at 0.70 USD is 875 cents in the list and in the summary total, the twenty-first trip in one calendar month is refused with nothing written while a trip dated in another month logs, the second effective-dated rate is the Pro series while overwriting stays free, and the only files written are trips.json, rates.json and counter.json.
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/mileage-log/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 Mileage Log 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: Twenty trips per calendar month, counted on the month of the trip date, so reconstructing last year's log at tax time does not consume this month's allowance. The trip list and the summary are never metered, and one rate per jurisdiction and category is free, overwriting it included. 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 Mileage Log for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Mileage Log produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Mileage Log 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