Home · Setup · Claude.ai and Claude Desktop connectors
Statutory travel allowances on the rate tables the tax authorities publish, and the trips you priced with them. It prices one business trip against a bundled rate table and shows the arithmetic that produced the number: the allowance per day, the partial-day fraction the scheme's own ladder gave, every deduction for a meal somebody else paid for, and the total in the scheme's own currency. Three schemes ship with it, the Polish delegation regulation at home and per country, the HMRC benchmark scale rates for travel inside the UK, and the US GSA CONUS standard M&IE with the lodging cap. Start and end are instants rather than wall clocks, so a trip across a clock change is 23 or 25 hours, and the Polish 24-hour period and the US calendar day give different and equally correct answers to the same trip. Trips can be saved under a name with a TRIP-YYYY-NNNN id, listed with a total per currency, reported per scheme and per month, and handed to the expense tracker as ready-made expense_add arguments. The tables are files inside the package rather than a feed, so the same trip priced twice gives the same answer, and every rate carries its authority, instrument, source URL and effective date.
Every rate this server quotes is a file inside the package rather than a call to a tax authority, so the hosted route answers a calculation with no network access of its own and gives the same figure as a local install; saved trips live in the hosted store behind the token, and trip_export hands back expense_add arguments as text, which is exactly what the expense-tracker connector on the same token takes.
| You say | Tool |
|---|---|
| What is the per diem for 58 hours in Krakow, leaving Tuesday at 8am, with breakfast provided on the first day and two hotel nights? | perdiem_calc |
| Price the same trip under the HMRC benchmark rates instead. | perdiem_calc |
| Save that as the Krakow audit trip and show me what I have claimed this quarter. | trip_record |
A destination that is not in the bundled table is refused by name rather than priced at a neighbour's rate. Measured through a real client on 2026-09-05: asked for a Polish per diem for Oman, the model called perdiem_calc, got back the server's own refusal (Poland domestic plus 34 countries abroad are bundled, so a missing country means not verified here rather than no rate exists), called perdiem_rates to check the coverage for itself, and then said plainly that it would not guess a number. An earlier build of this server answered that same trip with Romania's EUR 42.00 diet, because "romania".includes("oman") is true; the fallback is a prefix match now. In the same session a 58-hour Krakow trip came back at PLN 258.75, PLN 123.75 of diets plus PLN 135.00 of lodging ryczalt, with the arguments assembled from the prose unprompted.
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/per-diem/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 Per Diem 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: Rate lookups and calculations are unlimited on every tier, on all three schemes: the tables are public regulation, and metering the reading of a regulation would be charging for the tax authority's work rather than for this server's. 5 trips saved a calendar month, counted by start date, and unlimited trip lists. 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 Per Diem for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Per Diem produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Per Diem 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