Job cards for trades and field service: hours and materials per job, open to invoiced.
Category: Time and operations · Tools: 9 · Version: 0.22.6 · Licence: MIT
https://mcp.zovo.one/mcp/job-card/t/<token>. Paste that into your client. The bare https://mcp.zovo.one/mcp/job-card hands out the tool list but answers tool calls with HTTP 401, which is why the tokenised URL is the one to use..mcpb bundlegit clone https://github.com/theluckystrike/mcp-servers then build servers/job-card.@theluckystrike/mcp-job-card is staged and publishes shortly; the .mcpb bundle is the supported install until then.| Tool | What it does |
|---|---|
job_card_create |
see tool reference |
job_card_log_labor |
see tool reference |
job_card_log_material |
see tool reference |
job_card_update_status |
see tool reference |
job_card_list |
see tool reference |
job_card_get |
see tool reference |
job_card_print |
see tool reference |
job_card_delete |
see tool reference |
job_card_summary |
see tool reference |
Free to run locally, forever. The Pro licence is $19, one time, lifetime — it changes only the hosted endpoint’s saved-report cap, never the tools. All 58 servers together are $39 as a bundle instead of $1102 bought one at a time.
Buy the Job Card Pro licence — $19
Yes. Running Job Card locally is free and unlimited, and the code is MIT licensed. There is a one-time $19 Pro licence for the hosted endpoint, which removes the saved-report cap. No subscription and no account are required.
No. The server works offline against local files. If you use the hosted endpoint, the connection is authenticated with a scoped token instead of a per-tool API key.
Local installs keep everything on your machine. The hosted endpoint stores records in an isolated per-tenant namespace, and only for servers you actually call.
Any MCP client: Claude Desktop (via the .mcpb bundle), Claude Code, Cursor, Windsurf, VS Code with an MCP extension, or your own agent over the Streamable HTTP transport.
All 58 back-office MCP servers · how the collection is organised