# job card [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/theluckystrike/mcp-job-card  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/job-card

## Description
Job cards for trades and field service: hours and materials per job, open to invoiced.

## Tools
Capabilities this server exposes over MCP:

- **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** — Free or Pro, and the key

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "job-card": {
    "command": "npx",
    "args": ["-y","@theluckystrike/mcp-job-card"]
  }
}
```

## Documentation

## What job card MCP server does

The job card MCP server keeps one record for each field-service or trade job. A card includes the client, site, job description, currency, and scheduled date, then accumulates labor and material entries as work progresses. New cards receive identifiers in the `JC-YYYY-NNNN` format.

Labor entries store the worker, work date, hours, hourly rate in cents, and a description of the work. Material entries store the item, quantity, and unit cost in cents. The card maintains labor, materials, and combined totals. It can also record a controlled status sequence: `open`, `in_progress`, `done`, `invoiced`, and `archived`.

A printable card is available as Markdown or self-contained HTML and includes a client signature line. Daily and weekly summaries show touched cards, hours by worker, and labor and material values grouped by currency. Weekly reporting runs from Monday through Sunday.

## How it works

The job card MCP server exposes the record operations through MCP. Create a card, add labor or materials, inspect or list cards, and advance the status one step at a time. Status changes add a date and note to the card history. A card containing labor or material entries cannot be deleted; it must be archived instead.

Amounts are stored as integer cents. Labor and material line values are rounded half-up to the nearest cent when logged, and totals are calculated from those stored line values. Hours use integer hundredths and quantities use integer thousandths. Values in different currencies are kept separate; the server does not perform currency conversion.

The local installation stores data in `${XDG_DATA_HOME:-~/.local/share}/mcp-servers/job-card/`, using `cards.json` and `counter.json`. The local server does not make network calls, and license keys are checked offline. A hosted streamable-HTTP option is also documented and requires a bearer token.

## Setup and configuration

For a local setup, clone the repository, run `npm install && npm run build`, and configure an MCP client to launch `dist/index.js` with Node. The repository states that its vendored dependencies allow a fresh clone to build without additional dependency setup.

Claude Desktop can also use the downloadable `job-card.mcpb` release package. Claude Code and Cursor have documented MCP configuration examples. The package is not published on npm yet, so an `npx -y @theluckystrike/mcp-job-card` installation currently fails.

The hosted endpoint is `https://mcp.zovo.one/mcp/job-card`. It accepts a token through the `Authorization: Bearer <token>` header or through the `/t/<token>` path form. Calling tools without a token returns HTTP 401.

## Tools and capabilities

- `job_card_create`: create a card and return its identifier.
- `job_card_log_labor`: add worker hours and labor details.
- `job_card_log_material`: add used materials and costs.
- `job_card_update_status`: advance the card and append history.
- `job_card_list` and `job_card_get`: find cards or inspect one in full.
- `job_card_print`: render Markdown or HTML for printing.
- `job_card_summary`: report daily or weekly activity.
- `job_card_delete`: remove an empty, mistaken card.
- `license_status` and `license_activate`: inspect or manage the license state.

Free usage allows 10 active cards; Pro removes that active-card limit. Labor and material entries, totals, printing, and summaries are available in both tiers.

## Limitations and notes

The job card MCP server does not exchange currencies, and it prevents deletion once a card holds labor or material entries. The npm package is not currently available, so source builds, the Claude Desktop package, or the hosted endpoint are the documented working paths. Local data remains on the machine, while hosted use is a separate deployment option that requires authentication.

_Full upstream README: https://allmcps.com/mcp/job-card/readme_