Home · Guides

Produce a delivery schedule and a work order from a chat

A trade business raises a work order and tracks a delivery schedule, and people usually ask for both at once. They are not the same document: a work order says what will be done, by whom and at what price, and a delivery schedule says what is owed and when, with its whole job being answering what is late. Two MCP servers cover the pair.

The work order server

MCP Work Order registers a work order from a sentence, applies markup at the unit cost rather than the line total, and hands the finished job to the invoice server at the prices the work order carried, so nothing is retyped.

The delivery schedule server

MCP Delivery Schedule records what is owed and when, and answers what is late. It is the tracking half of the pair, the record you check rather than the document you send.

Install both

One click, with no JSON. Download work-order.mcpb and delivery-schedule.mcpb from the latest release and open them in Claude Desktop. They run on the Node runtime Claude Desktop ships with, so your own PATH and node version never come into it.

Or a URL, with nothing installed. /mcp/connect mints a free anonymous token and prints the ready lines:

claude mcp add --transport http work-order        https://mcp.zovo.one/mcp/work-order/t/<token>
claude mcp add --transport http delivery-schedule https://mcp.zovo.one/mcp/delivery-schedule/t/<token>

Or from a clone, for a client with no bundle installer. Build once, then point the client at the built file:

git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/work-order -w servers/delivery-schedule

claude mcp add --scope user work-order        -- node /absolute/path/to/mcp-servers/servers/work-order/dist/index.js
claude mcp add --scope user delivery-schedule -- node /absolute/path/to/mcp-servers/servers/delivery-schedule/dist/index.js

Claude Desktop, Cursor, Windsurf and Cline take the same two strings as JSON, in claude_desktop_config.json or the client's own MCP config file:

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

The npm packages are not published yet, so the npx form below returns a 404 today. It is kept because it is what that config becomes the day the publish lands, with nothing else changed; installing these servers when npx does not work yet has the whole picture.

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

There is no account and no API key. For the full walkthrough of the two documents and their pricing see delivery schedules and work orders from MCP.

Questions

Can an MCP server produce a work order?

Yes. MCP Work Order registers a work order from a sentence, applies markup at the unit cost, and hands the finished job to the invoice server at the prices the work order carried.

What is the difference between a work order and a delivery schedule?

A work order says what will be done, by whom and at what price. A delivery schedule says what is owed and when, and its whole job is answering what is late.

Do I need to install anything?

No. Both servers are hosted at mcp.zovo.one, so you can add them by URL with a free anonymous token and nothing installed locally.

All MCP servers and prices · All guides · Buy the bundle $39