Home · Setup · Claude.ai and Claude Desktop connectors
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.
The register lives in the hosted store behind the token, so the three free assets and the AST-YYYY-NNNN numbers follow the key rather than the machine. There is no network call inside the server on any route, so the due report is computed from the stored dates against today identically here and on a laptop - overdue is a reading, never something stored that could go stale. maintenance_export's CSV comes back in the answer itself, because a hosted call has nowhere local to write it.
| 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.
https://mcp.zovo.one/mcp/connect mints an anonymous token and prints a URL per server, including this one, shaped like https://mcp.zovo.one/mcp/maintenance-log/t/<token>. That URL works with no headers: the token is in the path, not in an Authorization field this form does not have.
Idle anonymous tokens are swept after 30 days. Since this route has no filesystem, a file MCP Maintenance Log generates comes back as a download link that expires after one hour. A Pro key can replace the token in the same URL and removes the free-tier limits.
On an individual Pro or Max plan you add the connector yourself from Customize, Connectors. On Team and Enterprise it is the other way round: only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, and members then connect to what the Owner added rather than pasting their own URL.
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, and binds to the token after checkout.
No. Add custom connector offers an Advanced settings section with an OAuth Client ID and Client Secret, but the connect-by-URL route does not use it. Leave both blank: the token in the URL path is what authenticates.
That is documented, not a bug: on Team and Enterprise, only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, Add, Custom, Web. After that, members connect to the URL the Owner added from Customize, Connectors.
Yes. The token segment of the URL from /mcp/connect can be replaced with a Pro key, which removes the free-tier limits on MCP Maintenance Log for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Maintenance Log produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Maintenance Log in detail · How connect-by-URL works · Every server for Claude.ai and Claude Desktop connectors · All clients · Claude.ai and Claude Desktop connectors docs · Buy Pro