Home · Setup · VS Code

MCP Delivery Schedule in VS Code

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.

In agent mode milestone_payload is a pure derivation that posts nothing: it returns invoice_create items in MAJOR units and quote_create items in MINOR units together and says posted false. The same milestone is exactly 100x apart in the two payloads, so take the payload named for the tool you are about to call and change no number in it.

What you get in VS Code

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.

Install it in VS Code

The file is .vscode/mcp.json, and the key inside it is servers.

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. VS Code reads its own config, so here it is:

// .vscode/mcp.json  (the key is "servers")
{
  "servers": {
    "delivery-schedule": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/delivery-schedule/dist/index.js"]
    }
  }
}

Or from a terminal:

code --add-mcp '{"name":"delivery-schedule","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-schedule

That 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:

code --add-mcp '{"name":"delivery-schedule","command":"npx","args":["-y","@theluckystrike/mcp-delivery-schedule"]}'

VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.

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.

No install: the hosted endpoint

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.

{
  "servers": {
    "delivery-schedule": {
      "url": "https://mcp.zovo.one/mcp/delivery-schedule",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

VS Code notes worth knowing first

The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.

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.

Questions

Why does my mcp.json do nothing?

The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.

Do I have to edit the file at all?

No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.

Where do the MCP Delivery Schedule tools show up?

In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.

Related

MCP Delivery Schedule in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro

Related guides & tools

Producing a delivery schedule or a work order document from a chat