Mileage Logbook

io.github.theluckystrikePublished by GitHub account theluckystrikev0.22.5Updated Nov 4, 2026

A mileage logbook for deductible driving: trips, effective-dated rates, summaries, CSV export.

VerifiedSTDIODesktop onlyProductivity & WorkflowFinanceData & Analytics

Overview

AI-generated overview

A local mileage logbook MCP server that lets an assistant record deductible trips, manage effective-dated rates, summarize amounts and export CSV.

What you can do
  • Log, list and remove trips with date, route, distance, purpose and category
  • Set and list effective-dated mileage rates per jurisdiction, category and unit
  • Summarize a date range by category, rate and deductible amount per currency
  • Export the log as CSV for an accountant (Pro)
  • Check or activate a license key
When to use it
Useful for freelancers and self-employed users who need a deductible driving log kept as trips happen, priced at the rate in force on each trip date, and handed to an accountant as CSV.
Requirements
Runs as a local process on the desktop, installed via the mcpb package or a clone-and-build (the npm package is not yet published). Node.js is needed for the npx-based configuration. No account, API key or network access is required; an optional Pro license key goes in MCP_LICENSE_KEY.
Before you install
Data is stored locally in a data directory on the machine. Free tier caps trips at 20 per calendar month and blocks CSV export; Pro costs $19 one-time (or $39 for a bundle) and is activated with a license key. No rates ship with the server, so entered figures must be verified; nothing it computes is tax advice. Removing a trip is permanent and its id is not reissued.

Installation

In SourceWeft

  1. Open Mileage Logbook in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

json
{  "mcpServers": {    "mileage-log": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-mileage-log"]    }  }}

Claude Code

sh
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):

text
rate_set jurisdiction:"US federal (EXAMPLE)" category:business    rate:0.70  unit:miles currency:USD effective_from:2026-01-01rate_set jurisdiction:"US federal (EXAMPLE)" category:business    rate:0.655 unit:miles currency:USD effective_from:2025-01-01rate_set jurisdiction:"US federal (EXAMPLE)" category:medical     rate:0.21  unit:miles currency:USD effective_from:2026-01-01rate_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:

Source: servers/mileage-log/README.md at commit 55b3f42

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.22.5LatestOct 14, 2026
  2. v0.22.0Sep 23, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts