INDIVIDUAL MCP TOOL

deliverable_add

Add one dated deliverable and return its D number and the new counts.

zovo.onenone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.zovo.one/mcp/delivery-schedule

No auth detected

Connect to this endpoint to inspect the live schema for deliverable_add and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mcp-delivery-schedule]
url = "https://mcp.zovo.one/mcp/delivery-schedule"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "mcp-delivery-schedule": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/delivery-schedule"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: mcp-delivery-schedule
Remote MCP URL: https://mcp.zovo.one/mcp/delivery-schedule

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-delivery-schedule": {
      "url": "https://mcp.zovo.one/mcp/delivery-schedule"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "mcp-delivery-schedule": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/delivery-schedule"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "mcp-delivery-schedule",
  "transport": "streamable-http",
  "url": "https://mcp.zovo.one/mcp/delivery-schedule"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

delivery_schedule_create — Open a delivery schedule against a quote, work order or change order and return its DS-YYYY-NNNN number: the reference, its own date, the client, a title and the currency.
deliverable_status — Record a dated move on one deliverable: planned, in_progress, delivered, then accepted with a note.
deliverable_delete — Delete one deliverable still planned with no history.
delivery_schedule_get — Return one schedule in full as at a date: every deliverable with due date, status, delivered and accepted dates, note and value, plus what is late and the totals.
delivery_schedule_list — List schedules oldest reference first with client, currency and counts as at a date: late, still owed, accepted.
delivery_schedule_delete — Delete a schedule carrying no deliverables, freeing an open slot.
late_report — What has slipped as at a date: every deliverable still owed past its due date, worst first, with value at risk per currency, and what was delivered late kept apart.
delivery_schedule_document — Render one schedule as a plain-text document for the client: every deliverable with its due date, status, delivered and accepted dates and value, the counts as at a date, and a sign-off block.