Home · Setup · Claude.ai and Claude Desktop connectors
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 schedules live in the hosted store behind the token, so the three free open schedules and the DS-YYYY-NNNN numbers follow the key rather than the machine, and the currency and VAT fallback on the document come from the shared business profile behind that same token. There is no network call inside the server on any route, so late means the same thing here as on a laptop: derived from the due dates against the as_of you pass, never stored, never read off the machine's clock. delivery_schedule_document comes back inline as the text with the sign-off block, so there is no download to chase; milestone_payload hands back the invoice and quote arguments as text for the invoice or quotes connector on the same token.
| 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.
https://mcp.zovo.one/mcp/connect mints an anonymous token and prints a URL per server, including this one, shaped like https://mcp.zovo.one/mcp/delivery-schedule/t/<token>. That URL works with no headers: the token is in the path, not in an Authorization field this form does not have.
Idle anonymous tokens are swept after 30 days. Since this route has no filesystem, a file MCP Delivery Schedule generates comes back as a download link that expires after one hour. A Pro key can replace the token in the same URL and removes the free-tier limits.
On an individual Pro or Max plan you add the connector yourself from Customize, Connectors. On Team and Enterprise it is the other way round: only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, and members then connect to what the Owner added rather than pasting their own URL.
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, and binds to the token after checkout.
No. Add custom connector offers an Advanced settings section with an OAuth Client ID and Client Secret, but the connect-by-URL route does not use it. Leave both blank: the token in the URL path is what authenticates.
That is documented, not a bug: on Team and Enterprise, only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, Add, Custom, Web. After that, members connect to the URL the Owner added from Customize, Connectors.
Yes. The token segment of the URL from /mcp/connect can be replaced with a Pro key, which removes the free-tier limits on MCP Delivery Schedule for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Delivery Schedule produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Delivery Schedule in detail · How connect-by-URL works · Every server for Claude.ai and Claude Desktop connectors · All clients · Claude.ai and Claude Desktop connectors docs · Buy Pro
Producing a delivery schedule or a work order document from a chat