io.github.theluckystrike/job-card MCP Server

The MCP server manages job-card style work orders end to end, from raising a work order against a client record through scheduling a visit, logging parts and hours, signing off, and billing. It records labour as hours at a rate and parts as quantities at unit cost with an optional markup, moving through workflow steps.

🛠️ Key Features

Schedule the visit
Raise work order against a client record used for invoices
Track site address and requested date; record job and urgency
Log labour hours (rate) and parts (quantity, unit cost, optional markup)
Move workflow: draft → scheduled → in progress → done → invoiced
Stamp each workflow step with date and note
Provide completion report with hours and materials

🚀 Use Cases

Trades and field work job cards
Client-based invoicing tied to work orders
Time tracking and parts/price tracking via spreadsheets-style records

⚡ Developer Benefits

Topics include typescript, MCP, Model Context Protocol, and time/price tracking use cases
Aligns work-order data with invoice client records

⚠️ Limitations

Only behavior described in the excerpt is reflected; no additional capabilities are provided in the source data.

mcp-job-card

In the official MCP Registry (io.github.theluckystrike/job-card). One card per job, the way the paper one on the dashboard works. Open a card for the client and the site, log the hours each worker puts in at their rate and the materials that go into the job, and the card keeps the running totals: labor, materials and the grand total, always in integer cents. Move the card along as the job moves, open, in progress, done, invoiced, archived, and when the client wants to see it, print the card with its signature line for sign-off. A daily or weekly summary answers where the crew's hours went and what the work is worth, per currency. Everything stays on this machine; there is no account and no network call.

Built by theluckystrike.

npm publish for @theluckystrike/mcp-job-card is pending, so npx -y @theluckystrike/mcp-job-card 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": {
    "job-card": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-job-card"]
    }
  }
}

Claude Code

claude mcp add job-card -- npx -y @theluckystrike/mcp-job-card

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.

Tools

tool	what it does
`job_card_create`	Open a job card: client, site, what the job is, currency, scheduled date. Returns `JC-YYYY-NNNN`
`job_card_log_labor`	Log hours on a job card: who did the work, the day, the hours, the hourly rate in cents, what was done
`job_card_log_material`	Log materials used on a job card: the item, the quantity, the unit cost in cents
`job_card_update_status`	Move the card exactly one step -- open, in_progress, done, invoiced, archived -- stamping date and note into its history
`job_card_list`	List cards newest first with hours and totals; filter by status and client; totals kept per currency
`job_card_get`	Read one card in full: every entry, hours per worker, and the running totals in integer cents
`job_card_print`	Render the card ready to print, with a signature line for client sign-off. Markdown or self-contained HTML
`job_card_delete`	Delete a card entered by mistake. One holding labor or materials is refused; archive it instead
`job_card_summary`	A day or a week: cards touched, hours per worker, labor and materials value per currency. A week runs Monday to Sunday
`license_status` / `license_activate`	Free or Pro, and the key

Free vs Pro

	Free	Pro
Active job cards	10	Unlimited
Labor and material entries per card	Unlimited	Unlimited
Running totals, list and get	Yes	Yes
Printable card, markdown and HTML	Yes	Yes
Daily and weekly summary	Yes	Yes

The record is never metered. Ten active cards is a real working board for a small crew, and a card stops counting the moment it is archived, so logging, totals, printing and summaries stay free for good. What Pro lifts is how many jobs are on the board at once.

Get Pro: https://mcp.zovo.one/buy/job-card, $19 one-time for this server, or $39 for the bundle.

Money and rounding

Every amount is an integer number of cents (a cent is 1/100 of the currency unit). A labor line is hours times the hourly rate; a materials line is quantity times the unit cost; each line value is rounded half-up to the nearest cent once, at the moment it is logged, and stored on the entry. Totals are the sums of those stored line values, so a total can never drift from its lines. Hours are carried as integer hundredths and quantities as integer thousandths, so 2.5 hours at 4999 cents an hour is 12498 cents, never 12497.499999. Currencies are never added together: this server holds no exchange rate.

Privacy

All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/job-card/. Two files: cards.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:

Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-job-card

client	string	required	Who the job is for, e.g. Kowalski bathroom refit, or Acme Ltd
site	string	required	Where the job is, e.g. 14 Nowa Street, flat 3
description	string	required	What the job is, e.g. Replace the consumer unit and certify
currency	string	required	ISO code the rates and prices are in
scheduled_date	string	optional	The date the crew is due on site, YYYY-MM-DD. May be in the future; it is a plan, not a log
note	string	optional

card	string	required	The job card id, e.g. JC-2026-0003, or the client name when only one card has it
worker	string	required	Who did the work, e.g. Anna
date	string	required	The day the work was done, YYYY-MM-DD. A future date is refused
hours	number	required	Hours worked, to the hundredth, e.g. 7.5 or 3.25. One entry is one worker's day at most
rate_cents	integer	required	The hourly rate in whole cents. 4500 is 45.00 an hour
note	string	optional	What was done, e.g. First fix, kitchen ring main

card	string	required	The job card id, e.g. JC-2026-0003, or the client name when only one card has it
item	string	required	What went into the job, e.g. Copper pipe 15mm, or Consumer unit 10-way
date	string	required	The day it went in, YYYY-MM-DD. A future date is refused
qty	number	required	How many, to the thousandth, e.g. 2 or 0.5
unit_cost_cents	integer	required	What one costs in whole cents. 1299 is 12.99
note	string	optional

card	string	required	The job card id, e.g. JC-2026-0003, or the client name when only one card has it
status	string	required	The next step for this card: open, in_progress, done, invoiced, archived. in-progress is accepted too
date	string	optional	The date to stamp the step with, YYYY-MM-DD. Default today
note	string	optional

card	string	required	The job card id, e.g. JC-2026-0003, or the client name when only one card has it
format	string	optional	markdown (default) or html. The HTML carries its own styling and references nothing external

io.github.theluckystrike/job-card

io.github.theluckystrike/job-card MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

job_card_create

job_card_log_labor

job_card_log_material

job_card_update_status

job_card_list

job_card_get

job_card_print

job_card_delete

job_card_summary

license_status

license_activate

mcp-job-card

Install

Claude Desktop

Claude Code

Cursor

Tools

Free vs Pro

Money and rounding

Privacy

Use these docs as an MCP server

Install

Remote endpoint

Configuration

Related servers