Maintenance Schedule

io.github.theluckystrikePublished by GitHub account theluckystrikev0.22.5Updated Oct 24, 2026

An equipment maintenance schedule and log: service entries, costs, and what is due or overdue.

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

A local equipment maintenance register that lets an assistant add assets, log service work and costs, and report what is due or overdue.

What you can do
  • Add and remove assets with name, serial or asset tag, location, notes and currency
  • Log service or repair work with date, description, cost in cents, technician and next due date or interval
  • Report what is overdue, what falls due within N days and what has no schedule (Pro)
  • Show one asset's full chronological history, total spend and spend per technician
  • Export entries in a date range as CSV or a Markdown summary per asset
  • Check or activate a free or Pro license
When to use it
Useful for keeping one local register of equipment you look after — workshop machines, rental flats, a van fleet or studio gear — and asking the assistant what service is coming up or overdue.
Requirements
Runs as a local process on the desktop via an mcpb package or a clone-and-build install; the npm package is not published yet, so npx currently fails. No account, API key or network call. An optional Pro license key is supplied through the MCP_LICENSE_KEY environment variable and verified offline.
Before you install
Pro features (unlimited assets, the due report, Markdown summaries) require a paid one-time license key; the free tier is limited to three assets. Removing an asset that has a log requires explicit confirmation and is permanent, since asset numbers are never reissued. Data is stored in local JSON files on the machine.

Installation

In SourceWeft

  1. Open Maintenance Schedule 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-maintenance-log

[theluckystrike/mcp-maintenance-log MCP server]

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.

Install

Claude Desktop

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

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

Claude Code

sh
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

toolwhat it does
asset_addAdd an asset: name, serial or asset tag, location, notes, currency. Returns AST-YYYY-NNNN. A duplicate tag is refused
maintenance_logLog work on an asset: the day, what was done, cost in cents, technician, and the next due date -- as next_due or as interval_days, never both
maintenance_dueThe due report: what is overdue and by how many days, what falls due within N days (default 30), what is scheduled later, what has no schedule. Pro
asset_historyOne asset in full: every entry in chronological order, total spend in integer cents, spend per technician, the schedule it currently lives under
maintenance_exportEntries in a date range as CSV (free) or a Markdown summary per asset (Pro)
asset_removeRemove an asset. One carrying a log is refused unless confirm: true, naming what would be lost. The AST number is never reissued
license_status / license_activateFree or Pro, and the key

Free vs Pro

FreePro
Assets on the register3Unlimited
Logging work, cost and technicianYesYes
Per-asset history and total spendYesYes
CSV export of a date rangeYesYes
Due report: overdue and due-within-N-days--Yes
Markdown summary per asset--Yes

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:

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