Home · Setup · Claude Desktop
Dated deliverables against a quote, a work order or a change order, and what is late as at any date you name. You open a schedule against the document that ordered the work, and add the deliverables: what is being handed over, the day it is due, its value in whole minor units when it is separately priced. Each deliverable moves planned to in progress to delivered to accepted, every step stamped with the day it actually happened, and acceptance is refused until the delivery is recorded, because acceptance is the client's answer to a handover. late_report answers what has slipped as at a date you name, worst first, with the value at risk per currency. milestone_payload hands the delivered-and-accepted milestones back as invoice_create-ready items in major units and quote_create-ready items in minor units at once, with the scale printed against each. No lateness is stored: a stored late flag is a fact about the afternoon somebody last ran the report, so lateness is derived on the call against the date you pass.
The client's email accepting a deliverable is usually already in this window, so recording the delivery and then the acceptance with the day each happened is one sentence against the thread, and the question that follows, what is late now, is the next one. Nothing leaves the machine: there is no network call in the server on any tool.
| You say | Tool |
|---|---|
| Open a delivery schedule against WO-2026-0011 for Harbour Cafe, dated 1 April: wireframes due the 10th at 900, the built site due 1 May at 2100. | delivery_schedule_create then deliverable_add |
| Wireframes went out on the 9th, signed off on the 12th. | deliverable_status |
| What was late as at 22 April? | late_report |
In the recorded probe the schedule carried wireframes at EUR 900.00, page copy at EUR 479.88 and the built site at EUR 2,100.00. As at 22 April the late report named the copy, late by 2 days, with EUR 47,988 minor at risk; as at 5 May it named the site, late by 4, with EUR 210,000 minor. The milestone payload then handed the two accepted deliverables back as [900, 479.88] in invoice_create's major units and [90000, 47988] in quote_create's minor units, exactly 100x apart, with the drift asserted to zero.
The file is claude_desktop_config.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
One click, with no JSON. Download delivery-schedule.mcpb from the
latest release and open it. Claude Desktop installs it as an extension and runs
it on the Node runtime it ships with, so neither your PATH nor your node version comes into it, and there
is no file to edit. Everything below is the manual route, for when you want the entry in the config file
itself.
The config block, which needs both strings absolute:
{
"mcpServers": {
"delivery-schedule": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/delivery-schedule/dist/index.js"]
}
}
}If node came from nvm, asdf or homebrew, use the absolute path that which node prints
rather than the bare word, because a stdio server started by this app inherits a limited PATH:
"command": "/Users/you/.nvm/versions/node/v22.14.0/bin/node"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/delivery-scheduleThat writes servers/delivery-schedule/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": {
"delivery-schedule": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-delivery-schedule"]
}
}
}Save, then completely quit Claude Desktop and start it again. A window reload is not enough.
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.
The same server runs at https://mcp.zovo.one/mcp/delivery-schedule over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"mcpServers": {
"delivery-schedule": {
"url": "https://mcp.zovo.one/mcp/delivery-schedule",
"headers": { "Authorization": "Bearer <token>" }
}
}
}Two documented facts decide whether the entry works: every path in claude_desktop_config.json must be absolute, and a stdio server started here inherits only a limited, platform-dependent subset of environment variables. If node came from nvm or homebrew, paste what `which node` prints instead of the bare word. The .mcpb route avoids both: Claude Desktop ships a built-in Node.js environment.
Free: Three open delivery schedules, and 200 deliverables on each on every tier. The cap counts the jobs that still owe something rather than the jobs ever scheduled, so completing one frees its slot, and deleting one frees it too. late_report is free on every tier: what has slipped is the question this server exists to answer. Pro is $19 once, verified offline.
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. There is no published Linux path. Settings, Developer, Edit Config opens the right copy and creates it if it does not exist.
In order: did you fully quit and restart, not just close the window? Is every path absolute? And is the command resolvable, given the limited environment a stdio server inherits here? If node came from nvm, paste what which node prints.
Yes. An .mcpb bundle, the format renamed from .dxt, opens with Claude and shows an installation dialog. One you built yourself goes in through Settings, Extensions, Advanced settings, Install Extension.
MCP Delivery Schedule in detail · The same server in Claude.ai and Claude Desktop connectors and Claude Code · Every server in Claude Desktop · Guides · Claude Desktop docs · Buy Pro
Producing a delivery schedule or a work order document from a chat