Home · Setup · Claude Code
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.
`claude mcp add job-card` at user scope is the level that matches both the meter and the data: ten active cards is a small crew's board rather than a repository's, and a card stops counting the moment it is archived, so finishing work is the way back under the cap rather than a key.
| 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 .mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| local (default) | ~/.claude.json, this project only |
| project | .mcp.json at the repository root |
| user | ~/.claude.json, every project |
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.
Claude Code reads its own config, so here it is:
From the terminal, against a built file:
claude mcp add --scope user job-card -- node /absolute/path/to/mcp-servers/servers/job-card/dist/index.js
claude mcp list # health-check it before the first prompt
# or --scope project, committed to .mcp.json for the teamThe 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:
claude mcp add job-card -- npx -y @theluckystrike/mcp-job-cardNo restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.
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 `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.
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.
Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.
Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.
Not this one. The office suite starts every sibling server as its own child process, so it runs locally over stdio. Thirty of those children are hosted individually at https://mcp.zovo.one/mcp/<name> if you want a no-install route; open https://mcp.zovo.one/mcp/connect and it prints a ready URL for each.
MCP Job Card in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro