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.
late_report is free, unlimited and writes nothing, so leave it enabled permanently and ask what has slipped as often as you like. deliverable_status is the tool that moves the record, and each step is dated, so an acceptance dated before the delivery is refused rather than stamped over.
| 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 .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
If you also run Claude Desktop, the shortest path there is one click: delivery-schedule.mcpb
from the latest release opens as an extension, with no JSON and no terminal.
Cursor reads its own config, so here it is:
The config block:
{
"mcpServers": {
"delivery-schedule": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/delivery-schedule/dist/index.js"]
}
}
}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"]
}
}
}The Customize page shows the server and its tools once it has started.
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>" }
}
}
}The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
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.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Delivery Schedule pasting the config block above is the supported route.
MCP Delivery Schedule in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro
Producing a delivery schedule or a work order document from a chat