mcpField
M
mileage-logbook

mileage-logbook

Local
mcp.zovo.oneFinance2Updated 1d ago

About mileage-logbook

mileage-logbook is a local MCP server for recording deductible trips, applying effective-dated rates, and producing summaries and CSV exports. It is suited to freelancers who need an auditable mileage log without sending data off-device.

Key features

  1. 01Record trips with dates, distance, purpose, and category
  2. 02Apply rates by jurisdiction, category, and effective date
  3. 03Summarize distance and deductible amounts by category
  4. 04Export mileage records as CSV
  5. 05Keep trip and rate data local

Use cases

  1. 01Track business and other categorized trips as they occur
  2. 02Apply a rate change to trips from its effective date
  3. 03Review yearly mileage totals for tax preparation
  4. 04Send a mileage CSV to an accountant

MCP support

It exposes trip, rate, summary, export, and license tools to MCP clients. It can be configured with clients such as Claude Desktop, Claude Code, and Cursor.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
mcpbmileage-log.mcpb0.22.5

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

mcp-mileage-log

theluckystrike/mcp-mileage-log MCP server

In the official MCP Registry (io.github.theluckystrike/mileage-log). An mcp mileage tracker that keeps the mileage log freelancers need at tax time, the moment the drive happens instead of reconstructed from memory in April. Log each trip with the date, from and to, the distance in miles or km, the purpose and the category (business, medical, moving, charitable, personal); set the rates that apply to you as an effective-dated series per jurisdiction and category; and the summary prices every trip at the rate in force on the day it was driven, per category and per currency. When the log is right, one call exports it as CSV to hand to your accountant. Everything stays on this machine; there is no account and no network call.

Built by theluckystrike.

npm publish for @theluckystrike/mcp-mileage-log is pending, so npx -y @theluckystrike/mcp-mileage-log returns 404 today. Until then, a clone+build is the working path.

Install

Claude Desktop

macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json:

{
  "mcpServers": {
    "mileage-log": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-mileage-log"]
    }
  }
}
Claude Code
claude mcp add mileage-log -- npx -y @theluckystrike/mcp-mileage-log
Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.

Tools

toolwhat it does
trip_addLog one trip: date, from, to, distance in miles or km, purpose, category. Returns TR-YYYY-NNNN
trip_listList trips oldest first, with the rate and amount each earns; filter by date range and category
trip_removeRemove a trip by its exact id, for entries made by mistake. The id is not reissued
rate_setSet what one mile or km is worth for one category in one jurisdiction from a date forward. A series, not one global number
rate_listEvery rate on file, grouped by jurisdiction and category with effective dates in order
mileage_summaryA date range (default the current year): per-category distance, the rate each trip earned, and the deductible amount, per currency
mileage_exportThe log as CSV for an accountant: date, from, to, distance, category, rate, amount. Pro
license_status / license_activateFree or Pro, and the key

Rates are a series, and none ship with the server

Tax authorities change their mileage rates, usually every year, so this server never holds one global rate: rate_set adds a rate for a jurisdiction, a category and a unit from an effective date, and each trip earns the rate in force on its own day. No rates ship with this server, and the example below is an EXAMPLE, not a statement of current law. Verify the figures that apply to you before you file.

An example rate set (illustrative only):

rate_set jurisdiction:"US federal (EXAMPLE)" category:business    rate:0.70  unit:miles currency:USD effective_from:2026-01-01
rate_set jurisdiction:"US federal (EXAMPLE)" category:business    rate:0.655 unit:miles currency:USD effective_from:2025-01-01
rate_set jurisdiction:"US federal (EXAMPLE)" category:medical     rate:0.21  unit:miles currency:USD effective_from:2026-01-01
rate_set jurisdiction:"US federal (EXAMPLE)" category:charitable  rate:0.14  unit:miles currency:USD effective_from:2026-01-01

A 2025 trip then prices at 0.655 and a 2026 trip at 0.70, automatically. If your trips are in km and your rate is per mile (or the other way around), the distance is converted with the exact factor (1 mile = 1.609344 km) before pricing.

Free vs Pro

FreePro
Trips per calendar month20Unlimited
Trip list and mileage summaryYesYes
Rates per jurisdiction and category1 (overwrite stays free)Unlimited series
CSV export for the accountantNoYes

The monthly cap is 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 log itself is never metered: reading, listing and summarizing stay free for good.

Get Pro: https://mcp.zovo.one/buy/mileage-log, $19 one-time for this server, or $39 for the bundle.

Money and rounding

A trip's deductible amount is its distance times the effective rate, rounded half-up to the cent per trip, and every total is the sum of those rounded per-trip amounts: a total can never drift from the lines it is made of, and the CSV export reconciles line by line with the summary. The arithmetic is integer-only (distances as thousandths of a unit, rates as thousandths of a currency unit), so 12.5 miles at 0.70 a mile is exactly 875 cents, never 874.99999. Miles and km are kept apart and never added together; amounts are kept per currency and never mixed. When a trip's unit differs from the rate's, the distance is converted first (1 mile = 1.609344 km exactly) and rounded half-up to the thousandth of the rate's unit, then priced.

Privacy

All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/mileage-log/. Three files: trips.json, rates.json, counter.json. Nothing is sent anywhere, there is no account, no API key and no network call in this server at all. License keys are verified offline. Nothing this server computes is tax advice; the rates you enter are your own figures to verify.

Built by theluckystrike. https://github.com/theluckystrike

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.