delivery_schedule_document — milestone schedule MCP Tool
delivery_schedule_document
(delivery schedule document) is one of 12 tools on the
milestone schedule
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call delivery_schedule_document from your client
- Claude Code milestone schedule delivery_schedule_document run in your project directory
- Claude Desktop milestone schedule delivery_schedule_document ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor milestone schedule delivery_schedule_document ~/.cursor/mcp.json
- VS Code milestone schedule delivery_schedule_document .vscode/mcp.json
- Zed milestone schedule delivery_schedule_document ~/.config/zed/settings.json
- Windsurf milestone schedule delivery_schedule_document ~/.codeium/windsurf/mcp_config.json
- Cline milestone schedule delivery_schedule_document ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI milestone schedule delivery_schedule_document ~/.gemini/settings.json
- Grok milestone schedule delivery_schedule_document .mcp.json (in your project root)
- ChatGPT milestone schedule delivery_schedule_document Settings → Connectors → Advanced → Developer mode
- Claude.ai milestone schedule delivery_schedule_document Settings → Connectors → Add custom connector
- LangChain milestone schedule delivery_schedule_document pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http milestone-schedule https://mcp.zovo.one/mcp/milestone-scheduleOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.