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.
trip_list, rate_list and mileage_summary are free, unlimited and write nothing, so leave them enabled permanently and read the log as often as you like. trip_add is the deliberate one: a future date is refused, and when two jurisdictions price one category the call asks which, rather than guessing.
| 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.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
If you also run Claude Desktop, the shortest path there is one click: mileage-log.mcpb
from the latest release opens as an extension, with no JSON and no terminal.
Cursor reads its own config, so here it is:
The config block:
{
"mcpServers": {
"mileage-log": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/mileage-log/dist/index.js"]
}
}
}The node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/mileage-logThat writes servers/mileage-log/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
{
"mcpServers": {
"mileage-log": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-mileage-log"]
}
}
}The Customize page shows the server and its tools once it has started.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.
The same server runs at https://mcp.zovo.one/mcp/mileage-log over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"mcpServers": {
"mileage-log": {
"url": "https://mcp.zovo.one/mcp/mileage-log",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
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.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Mileage Log pasting the config block above is the supported route.
MCP Mileage Log in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro