Cline McpStamp Delivery Schedule delivery_schedule_create
How to: Cline McpStamp Delivery Schedule delivery_schedule_create
Add McpStamp Delivery Schedule to Cline
-
01
Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"deliverable-tracker": {
"url": "https://mcp.zovo.one/mcp/delivery-schedule"
}
}
}-
02
Save the file and restart Cline.
-
03
Ask for something delivery_schedule_create does. Cline lists the server's tools on connect and calls delivery_schedule_create itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that McpStamp Delivery Schedule's identifier in your config matches the one above exactly.
Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs
Set these first
McpStamp Delivery Schedule will not start until these are set, so delivery_schedule_create never becomes available.
-
MCP_LICENSE_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.