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.
In agent mode the due report is computed at call time from the stored dates, never stored itself, so an agent cannot quote a stale overdue list: maintenance_due re-derives it against today on every call, and an asset with no schedule is reported as unscheduled rather than invented onto one.
| 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.
The file is .vscode/mcp.json, and the key inside it is servers.
| Scope | Path |
|---|---|
| This workspace | <workspace>/.vscode/mcp.json |
| Every workspace | the user profile mcp.json, opened by the MCP: Open User Configuration command |
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.
VS Code reads its own config, so here it is:
// .vscode/mcp.json (the key is "servers")
{
"servers": {
"maintenance-log": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/maintenance-log/dist/index.js"]
}
}
}Or from a terminal:
code --add-mcp '{"name":"maintenance-log","command":"node","args":["/absolute/path/to/mcp-servers/servers/maintenance-log/dist/index.js"]}'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-logThat 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:
code --add-mcp '{"name":"maintenance-log","command":"npx","args":["-y","@theluckystrike/mcp-maintenance-log"]}'VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.
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.
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.
{
"servers": {
"maintenance-log": {
"url": "https://mcp.zovo.one/mcp/maintenance-log",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.
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.
The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.
No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.
In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.
MCP Maintenance Log in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro