Buyer problem: the workshop, the rental flats, the van fleet, the studio. Equipment needs a service record, and the usual way of running one is a spreadsheet plus someone's memory of when the last service was. The boiler gets serviced a month late because nobody could say when it was due. This server keeps one register of the equipment and the work done on it, and answers what is due from the dates on file, so nothing depends on anyone remembering.
asset_add records a machine with its name, serial or asset tag, location and currency,
returning an AST-YYYY-NNNN id. The serial or tag is unique across the register, so the same
boiler cannot be entered twice. 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 next_due or
interval_days, never both, so a date and an interval cannot fight each other.
maintenance_due is the reason to run this at all. At the moment you ask it answers what
is overdue and by how many days, what falls due within the next N days, and what has no schedule at all.
It computes from the stored dates, so the register cannot go stale between edits.
asset_history reads one asset's whole log in chronological order with its total spend in
integer cents and 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, and the
AST number is never reissued, so the history stays append-only in a way a spreadsheet is
not.
One click, no JSON. Download maintenance-log.mcpb from the
latest release and open it in Claude Desktop. It runs on the
Node runtime Claude Desktop ships with, so your own PATH and node version never come into it.
Or a URL, with nothing installed. /mcp/connect mints a free anonymous token and prints the ready line:
claude mcp add --transport http maintenance-log https://mcp.zovo.one/mcp/maintenance-log/t/<token>Or from a clone, for a client with no bundle installer. Build once, then point the client at the built file:
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
claude mcp add --scope user maintenance-log -- node /absolute/path/to/mcp-servers/servers/maintenance-log/dist/index.jsClaude Desktop, Cursor, Windsurf and Cline take the same two strings as JSON, in
claude_desktop_config.json or the client's own MCP config file:
{
"mcpServers": {
"maintenance-log": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/maintenance-log/dist/index.js"]
}
}
}The npm packages are not published yet, so the npx form below returns a 404 today. It is
kept because it is what that config becomes the day the publish lands, with nothing else changed;
installing these servers when npx does not work yet
has the whole picture.
claude mcp add maintenance-log -- npx -y @theluckystrike/mcp-maintenance-logWhichever path you take, there is no account, no API key and no login step. It writes to
~/.local/share/mcp-servers/maintenance-log/.
These are the sentences you type:
Add an asset. "Add the combi boiler, serial SN-88-4412, at 14 Nowa Street flat 3,
EUR." One call, one asset with an AST-YYYY-NNNN id.
Log the work. "Log the annual service on the 9th, 120.00 by Acme Heating, next due in 365 days." The cost in cents, the technician, and the next service date.
Ask what is due. "What is overdue or coming due this month?" Computed from the stored dates, most overdue first.
Export for the records. "Export this year's service log as CSV."
A spreadsheet can hold the rows, but it cannot answer "what is due" without you working out each date. The job this server does that a spreadsheet does not is the due report computed from dates you actually stored, plus the per-asset history with spend and spend per technician. That is the difference between a log you have to interrogate and a register that answers.
There is no direct MCP competitor: an npm registry probe for maintenance-log, maintenance-schedule, equipment log, service-log and maintenance found no other server that holds an equipment register with a due report.
Three assets on the register, with logging, the per-asset history with total spend and CSV export free and unlimited on every tier. Removing an asset frees its slot.
Pro ($19 once, lifetime) opens unlimited assets, the due report (overdue and due-within-N-days) and the Markdown summaries. The full comparison is in free versus Pro. Product page: MCP Maintenance Log. There are 41 of these MCP servers in total; one lifetime key covering all of them, this one included, is $39.
Claude.ai, the Claude Desktop connector dialog and several IDE pickers take a remote URL and nothing
else. mcp/connect mints a token and prints a ready-to-paste URL for every
hosted server, including this one at https://mcp.zovo.one/mcp/maintenance-log.
MCP Maintenance Log keeps one register of assets and the work done on them, and answers what is overdue or coming due from the stored dates the moment you ask. Three assets with CSV export are free; Pro is $19 once for unlimited assets and the due report.
maintenance_due reads the dates on file and answers what is overdue by how many days, what falls due within the next N days, and what has no schedule. It is computed at the moment you ask, so it cannot go stale.
Yes. asset_history reads one asset's whole log in chronological order with total spend in integer cents and spend per technician.
Yes. https://mcp.zovo.one/mcp/maintenance-log answers over streamable HTTP. mcp/connect mints a free anonymous token and prints the ready URL.
All MCP servers and prices · All guides · Buy the bundle $39