One card per job: hours and materials logged against it, a status machine from open to invoiced, and the printed card for client sign-off. You open a card for the client, the site, what the job is, the currency and the scheduled date, and it returns a JC-YYYY-NNNN id. The crew logs hours each at their rate and materials as item, quantity and unit cost, each line valued and rounded half-up to the cent once at the moment it is logged and stored on the entry, so the running totals are plain sums of stored line values and can never drift from the lines. Hours are carried as integer hundredths, so 2.5 hours at 4,999 cents an hour is 12,498 cents, never 12,497.499999. The card moves exactly one step at a time, open to in_progress to done to invoiced to archived, every step dated in its history, and a skipped or backwards step is refused. job_card_print renders the card with a signature line for client sign-off, and job_card_summary answers a day or a week: cards touched, hours per worker, value per currency, never mixed. A card holding labor or materials cannot be deleted, because it is the record of work done; it is archived instead, and the JC number is never reissued.
job_card_list, job_card_get, job_card_print and job_card_summary are free, unlimited and write nothing, so leave them enabled permanently and read the board as often as you like. job_card_update_status is the deliberate one: the card moves exactly one step at a time, every step is dated, and a skipped step is refused rather than stamped over.
| You say | Tool |
|---|---|
| Open a job card for the Kowalski bathroom refit, 14 Nowa Street flat 3: replace the consumer unit and certify, EUR, scheduled 2026-03-09. | job_card_create |
| Anna logged 7.5 hours at 45.00 an hour on the 9th, first fix. | job_card_log_labor |
| Print the card for the client to sign. | job_card_print |
On the worked card, 7.5 hours at 4,500 cents an hour is 33,750 cents and one consumer unit at 18,999 is 18,999, and the grand total is their plain sum, 52,749. The smoke suite drives create, log labor, log material, the one-step status moves, print in both formats, the summary and the delete guards over real stdio, then the free cap on the eleventh active card and the same calls passing in Pro.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
If you also run Claude Desktop, the shortest path there is one click: job-card.mcpb
from the latest release opens as an extension, with no JSON and no terminal.
Cursor reads its own config, so here it is:
The config block:
{
"mcpServers": {
"job-card": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/job-card/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/job-cardThat writes servers/job-card/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:
{
"mcpServers": {
"job-card": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-job-card"]
}
}
}The Customize page shows the server and its tools once it has started.
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.
There is no hosted endpoint for this one yet. MCP Job Card runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Thirty of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP; https://mcp.zovo.one/mcp/connect lists them and prints a ready URL for each.
The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: Ten active job cards, with labor and material entries unlimited per card and the running totals, list, get, the printable card and the daily and weekly summaries all free and unlimited on every tier. A card stops counting the moment it is archived, so the record is never metered. Pro is $19 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Job Card pasting the config block above is the supported route.
MCP Job Card in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro