Home · Setup · Claude Code

MCP Maintenance Log in Claude Code

Equipment maintenance log: assets, service entries with costs, and a due report computed from stored dates. You add each piece of equipment once - name, serial or asset tag, where it lives, the currency its costs are in - and it comes back with an AST-YYYY-NNNN id, a second asset with the same tag refused because a serial identifies one machine. maintenance_log records the work: the day, what was done, the cost in whole cents, who did it, and when the next service falls due, as a date or as an interval in days, never both, and a future work date is refused. maintenance_due is the report: what is overdue and by how many days, what falls due within the next N days (30 unless you say otherwise), what is scheduled later and what has no schedule at all, computed from the stored dates at the moment you ask, so the register cannot go stale. asset_history reads one asset's whole log in chronological order with the total spend in integer cents and the spend per technician, and maintenance_export hands a date range over as CSV or a Markdown summary per asset. An asset carrying a log cannot be removed without confirm: true, because removing it loses the record of work done; the AST number is never reissued.

`claude mcp add maintenance-log` at user scope is the level that matches both the meter and the data: three assets is a one-machine shop's register rather than a repository's, and removing a sold asset frees its slot, so the way back under the cap is the register being current, not a key.

What you get in Claude Code

You say	Tool
Add the combi boiler, serial SN-88-4412, at 14 Nowa Street flat 3, EUR.	`asset_add`
Log the annual service on the 9th, 120.00 by Acme Heating, next due in 365 days.	`maintenance_log`
What is overdue or coming due this month?	`maintenance_due`

The contract suite drives the eight tools over real stdio: the fourth asset is refused and nothing is written, a duplicate tag is refused, next_due and interval_days together are refused, a logged asset needs confirm to remove, and the only files written are assets.json and counter.json. The due report is asserted as computed at call time: an interval becomes a date once, at log time, and nothing about overdue is stored.

Install it in Claude Code

The file is .mcp.json, and the key inside it is mcpServers.

Scope	Path
local (default)	`~/.claude.json, this project only`
project	`.mcp.json at the repository root`
user	`~/.claude.json, every project`

If you also run Claude Desktop, the shortest path there is one click: maintenance-log.mcpb from the latest release opens as an extension, with no JSON and no terminal. Claude Code reads its own config, so here it is:

From the terminal, against a built file:

claude mcp add --scope user maintenance-log -- node /absolute/path/to/mcp-servers/servers/maintenance-log/dist/index.js
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

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/maintenance-log

That writes servers/maintenance-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:

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

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

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.

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/maintenance-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.

claude mcp add --transport http maintenance-log https://mcp.zovo.one/mcp/maintenance-log \
  --header "Authorization: Bearer <token>"

Claude Code notes worth knowing first

The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.

Free: Three assets on the register, with logging work, the per-asset history with its total spend and CSV export free and unlimited on every tier. Removing an asset frees its slot, so the record is never metered. Pro is $19 once, verified offline.

Questions

Which scope should I use for MCP Maintenance Log?

Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.

Why did my first prompt ignore the server?

Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.

Can I use MCP Maintenance Log without installing anything?

Yes: claude mcp add --transport http maintenance-log https://mcp.zovo.one/mcp/maintenance-log --header "Authorization: Bearer <token>". Mint a free token at https://mcp.zovo.one/mcp/token or use a Pro key. -t and -H are the short forms.

MCP Maintenance Log in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro