mcp-maintenance-log

MCP server for an equipment maintenance log and schedule: service entries, costs, and what is due or overdue. Equipment maintenance log: assets, service entries with costs, and a due report computed from stored dates.

Works with Claude Desktop, Claude Code, Cursor and any Model Context Protocol client. Runs on your own machine, or hosted with no install.

Product page: https://mcp.zovo.one/s/maintenance-log - what it does, the tools it exposes, and a live token endpoint.

Install

Hosted, nothing to install. Get a token from https://mcp.zovo.one/mcp/connect (the connect page) or https://mcp.zovo.one/mcp/token (the same token as JSON); a free anonymous one is issued on the spot and a Pro key works the same way. Then point an MCP client at https://mcp.zovo.one/mcp/maintenance-log over streamable-http and send the token as Authorization: Bearer <token>.

If your client cannot set headers, put the token in the path instead: https://mcp.zovo.one/mcp/maintenance-log/t/<token>. Both forms work. The bare URL with no token answers 401 on tools/call, so the token is not optional.

Claude Desktop, one click. Download maintenance-log.mcpb from the latest release and double-click it.

From source. The mirror is self-contained: every @theluckystrike/* dependency is vendored, so a fresh clone builds with no extra setup.

git clone https://github.com/theluckystrike/mcp-maintenance-log.git
cd mcp-maintenance-log
npm install && npm run build

Then point your client at the built entry point:

{
  "mcpServers": {
    "maintenance-log": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-maintenance-log/dist/index.js"]
    }
  }
}

@theluckystrike/mcp-maintenance-log is not published on npm yet, so an npx -y @theluckystrike/mcp-maintenance-log command will fail. The three paths above are the working ones and each is exercised by CI.

Read-only mirror of mcp-servers/servers/maintenance-log. See MIRROR.md.

In the official MCP Registry (io.github.theluckystrike/maintenance-log). An mcp maintenance log for the workshop, the rental flats, the van fleet or the studio: one local register of every piece of equipment you look after, and the work that has been done on it. Add each asset once, name, serial or asset tag, where it lives, then log each service or repair as it happens: the date, what was done, what it cost in cents, who did it, and when the next service falls due, either as a date or as an interval in days. Ask what is due and the report answers what is overdue and what comes up in the next N days, computed from the stored dates at the moment you ask, so it can never go stale. Per-asset history keeps the chronological log with its total spend, and export hands the record over as CSV for a spreadsheet or a Markdown summary per asset. Everything stays on this machine; there is no account and no network call.

Built by theluckystrike.

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

Related MCP server: HomeOps MCP

Install

Claude Desktop

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

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

Claude Code

claude mcp add maintenance-log -- npx -y @theluckystrike/mcp-maintenance-log

Cursor

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

Tools

Free vs Pro

The record is never metered. Three assets with full logging and CSV export is a real working register for a one-machine shop, and nothing you have logged is ever held back. What Pro lifts is how many assets are on the register, and adds the due report and the Markdown summaries.

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

Dates and money

Every date is stored as ISO 8601 (YYYY-MM-DD). Whether a service is overdue is computed from today's date at call time, never stored, so the register cannot go stale. An interval is turned into a date once, when the work is logged: the work date plus the interval, in whole days, in UTC so the answer does not depend on the server's timezone. Every cost is an integer number of cents in the asset's own currency (1200 is 12.00), stored on the entry; a total spend is the sum of the stored entries, so it can never drift from the lines it is made of.

Privacy

All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/maintenance-log/. Two files: assets.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.

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:

• Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-maintenance-log