Home · Setup · Cline

MCP Job Card in Cline

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 reads and safe to auto-approve. Keep job_card_log_labor and job_card_log_material behind a click, because each writes a line that totals are summed from, and remember job_card_delete refuses a card holding any entries: archive is the move, and it keeps the record. Nothing here writes into another server's store.

What you get in Cline

You sayTool
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.

Install it in Cline

The file is mcp.json, and the key inside it is mcpServers.

ScopePath
Cline CLI~/.cline/mcp.json
The editor extensionopened from the Cline panel, not by path; the documentation deliberately calls it the MCP settings JSON used by the extension

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. Cline reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "job-card": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/job-card/dist/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

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-card

That 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"]
    }
  }
}

No full-app restart. The MCP settings actions include restarting an unresponsive server if its tools do not appear.

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.

No install: the hosted endpoint

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.

Cline notes worth knowing first

Cline is the one client here with an unsafe transport default. `type` selects it, and omitting `type` falls back to the legacy sse transport, so a streamable HTTP endpoint needs it written in or you will debug a server that is fine. Local entries carry "disabled" and an "autoApprove" array.

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.

Questions

Where does the config live?

The CLI reads ~/.cline/mcp.json. For the extension, do not hunt for a path: MCP Servers icon, Configure tab, Configure MCP Servers. cline mcp opens a wizard, and cline config mcp --json is the non-interactive form.

The hosted endpoint will not connect.

Set the transport explicitly. Omitting type falls back to the legacy sse transport, so streamable HTTP needs "type": "streamableHttp" written in. It is the one default here that sends you debugging a server that works.

Should I auto-approve MCP Job Card's tools?

Approve the read-only ones and leave the writing ones behind a click: each entry carries an autoApprove array and a disabled flag.

Related

MCP Job Card in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs · Buy Pro