Work Order MCP

Work orders from chat: create, assign, track status and parts, close with labor totals. Pairs with quotes and job cards.

GitHubTry this MCPSponsored

Documentation

mcp-work-order

MCP server for work orders and job cards for trades and field service. Job orders for trades and field work, priced the way the invoice will be.

Works with Claude Desktop, Claude Code, Cursor and any Model Context Protocol client. Runs on your own machine, or hosted with no install.

Product page: https://mcp.zovo.one/s/work-order — what it does, the tools it exposes, and a live token endpoint.

Install

Hosted, nothing to install. Get a token from https://mcp.zovo.one/mcp/connect (the connect page) or https://mcp.zovo.one/mcp/token (the same token as JSON); a free anonymous one is issued on the spot and a Pro key works the same way. Then point an MCP client at https://mcp.zovo.one/mcp/work-order over streamable-http and send the token as Authorization: Bearer <token>.

If your client cannot set headers, put the token in the path instead: https://mcp.zovo.one/mcp/work-order/t/<token>. Both forms work. The bare URL with no token answers 401 on tools/call, so the token is not optional.

Claude Desktop, one click. Download work-order.mcpb from the latest release and double-click it.

From source. The mirror is self-contained: every @theluckystrike/* dependency is vendored, so a fresh clone builds with no extra setup.

git clone https://github.com/theluckystrike/mcp-work-order.git
cd mcp-work-order
npm install && npm run build

Then point your client at the built entry point:

{
  "mcpServers": {
    "work-order": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-work-order/dist/index.js"]
    }
  }
}

@theluckystrike/mcp-work-order is not published on npm yet, so an npx -y @theluckystrike/mcp-work-order command will fail. The three paths above are the working ones and each is exercised by CI.

work-order demo

Read-only mirror of mcp-servers/servers/work-order. See MIRROR.md.

In the official MCP Registry (io.github.theluckystrike/work-order). Job orders for trades and field work, kept the way a job card is kept. Raise a work order against a client (the same client record your invoices use), give it a site address, the date it was asked for, what the job is and how urgent. Log what the job actually used as it goes: labour as hours at a rate, parts as a quantity at a unit cost with an optional markup. Move it along one step at a time, draft to scheduled to in progress to done to invoiced, each step stamped with its date and a note. When it is finished, hand the customer a completion report with the hours, the materials, the totals and a sign-off block, and take the invoice payload straight to invoice_create without retyping a single figure.

Nothing is invented and nothing is stored twice: the value, the hours, the materials and the VAT are derived from the lines on every call, and the invoice payload's unit prices are already the billed units, so the invoice reproduces the work order to the minor unit.

npm publish for @theluckystrike/mcp-work-order is pending, so npx -y @theluckystrike/mcp-work-order returns 404 today. Until then, the .mcpb one-click bundle or a clone+build is the working path.

Install

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "work-order": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-work-order"]
    }
  }
}

Claude Code

claude mcp add work-order -- npx -y @theluckystrike/mcp-work-order

Cursor

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

Tools

Tool	What it does
`work_order_create`	Raise a job order and return its `WO-YYYY-NNNN` number: client, site address, requested date, description, priority
`work_order_add_line`	Add one line: parts with a quantity and a unit cost in minor units and an optional markup percent, or labour with hours and an hourly rate
`work_order_status`	Move it one step: draft, scheduled, in_progress, done, invoiced, stamping the date and a note
`work_order_get`	One work order in full: every line with its billed unit, the hours, the materials, net and VAT, and the status history
`work_order_list`	List work orders by status, by client and by requested-date range
`work_order_delete`	Delete a work order raised by mistake. Draft with no lines only. Free on every tier
`completion_report_text`	The completion report as plain text, ready to paste into an email
`completion_report_pdf`	The completion report as an A4 PDF, with the sign-off block
`work_order_invoice_payload`	An `invoice_create`-ready payload from the lines, with VAT at the shared profile rate
`work_orders_report`	The whole board: work orders per status, hours logged this month, unbilled value per currency
`license_status` / `license_activate`	Free or Pro, and where to upgrade

Free vs Pro

	Free	Pro
Open work orders	5	unlimited
Lines per work order	200	200
Raise, log, move, list, delete	yes	yes
Completion report (text)	yes	yes
Completion report (PDF)	no	yes
Invoice payload	no	yes
Board report	no	yes

The cap counts OPEN work orders (draft, scheduled, in progress), not the ones you have ever raised, so finishing a job frees its slot. So does work_order_delete on a draft that has no lines, which is free on every tier: a way back that only a Pro key can reach is not a way back.

Get Pro: https://mcp.zovo.one/buy/work-order (one-time $19, lifetime), or all servers for $39: https://mcp.zovo.one/buy/bundle

Where the money comes from

This server keeps no arithmetic of its own. computeTotals, currencyDecimals, formatMoney and roundHalfUp are imported from @theluckystrike/mcp-invoice/lib, the A4 renderer from @theluckystrike/mcp-billing-docs/lib, the corrupt-store quarantine from @theluckystrike/mcp-timezone/lib. The VAT rate, the currency and the business name come from the shared business profile that business_set in the invoice server writes; the client comes from that server's client records. Nothing is written outside this server's own directory.

The measured insight

A markup belongs on the unit cost, not on the line total, and one minor unit is what says so. Seven parts at EUR 12.99 with 15 percent on top is EUR 14.94 a unit and EUR 104.58 on the line. Marking up the line total instead is round(9093 * 1.15) = 10,457 minor units, a cent less. Both look like the same sum, and only one of them is the figure the customer will be billed: the invoice server rounds the unit price to the minor unit first and multiplies (its D-R24 basis), so a work order that quotes the line-total figure quotes a number its own invoice cannot reproduce. The gap appears on every line whose marked-up unit does not land on a whole cent, it never nets out across lines because it is a rounding direction and not an error, and it is invisible in a spreadsheet check because both bases add up correctly. The unit suite asserts the 1-unit gap explicitly, so a change of basis fails the build instead of quietly re-pricing every job on the board.

Privacy

All data stays on your machine, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/work-order/. Nothing is sent anywhere. There is no account and no API key. License keys are verified offline. This server reads one sibling file, the invoice server's clients.json, and writes into no store but its own.

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-work-order