mcpField
J
job-card

job-card

Remote
mcp.zovo.oneBusiness & Marketing2Updated 1d ago

About job-card

An MCP server for trades and field-service teams to track each job’s labor, materials, status, and totals. Records stay on the machine, with printable cards and daily or weekly summaries.

Key features

  1. 01Create and track job cards
  2. 02Log labor and materials
  3. 03Maintain per-currency totals
  4. 04Update job status and history
  5. 05Print cards for sign-off
  6. 06Summarize daily or weekly work

Use cases

  1. 01Track worker hours and materials by job
  2. 02Review labor and material costs
  3. 03Print a card for client approval
  4. 04Summarize crew hours for a week

MCP support

Exposes job-card creation, logging, status, reporting, and printing tools to MCP clients. Data remains local.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.zovo.one/mcp/job-card
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://mcp.zovo.one/mcp/job-cardAuth required
Packages
mcpbjob-card.mcpb0.22.5

Tools

11
ParameterTypeRequiredDescription
notestringNo
sitestringYesWhere the job is, e.g. 14 Nowa Street, flat 3
clientstringYesWho the job is for, e.g. Kowalski bathroom refit, or Acme Ltd
currencystringYesISO code the rates and prices are in
descriptionstringYesWhat the job is, e.g. Replace the consumer unit and certify
scheduled_datestringNoThe date the crew is due on site, YYYY-MM-DD. May be in the future; it is a plan, not a log

Details

From the project README

mcp-job-card

theluckystrike/mcp-job-card MCP server

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:

{
  "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

toolwhat it does
job_card_createOpen a job card: client, site, what the job is, currency, scheduled date. Returns JC-YYYY-NNNN
job_card_log_laborLog hours on a job card: who did the work, the day, the hours, the hourly rate in cents, what was done
job_card_log_materialLog materials used on a job card: the item, the quantity, the unit cost in cents
job_card_update_statusMove the card exactly one step -- open, in_progress, done, invoiced, archived -- stamping date and note into its history
job_card_listList cards newest first with hours and totals; filter by status and client; totals kept per currency
job_card_getRead one card in full: every entry, hours per worker, and the running totals in integer cents
job_card_printRender the card ready to print, with a signature line for client sign-off. Markdown or self-contained HTML
job_card_deleteDelete a card entered by mistake. One holding labor or materials is refused; archive it instead
job_card_summaryA day or a week: cards touched, hours per worker, labor and materials value per currency. A week runs Monday to Sunday
license_status / license_activateFree or Pro, and the key

Free vs Pro

FreePro
Active job cards10Unlimited
Labor and material entries per cardUnlimitedUnlimited
Running totals, list and getYesYes
Printable card, markdown and HTMLYesYes
Daily and weekly summaryYesYes

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:

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.