check_delivery — Camden Tools MCP Prompt

check_delivery is one of 3 prompts on the Camden Tools MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke check_delivery from your client

• Claude Code Camden Tools Prompt/check_delivery run in your project directory
• Claude Desktop Camden Tools Prompt/check_delivery ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Camden Tools Prompt/check_delivery ~/.cursor/mcp.json
• VS Code Camden Tools Prompt/check_delivery .vscode/mcp.json
• Zed Camden Tools Prompt/check_delivery ~/.config/zed/settings.json
• Windsurf Camden Tools Prompt/check_delivery ~/.codeium/windsurf/mcp_config.json
• Cline Camden Tools Prompt/check_delivery ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Camden Tools Prompt/check_delivery ~/.gemini/settings.json
• Grok Camden Tools Prompt/check_delivery .mcp.json (in your project root)
• ChatGPT Camden Tools Prompt/check_delivery Settings → Connectors → Advanced → Developer mode
• Claude.ai Camden Tools Prompt/check_delivery Settings → Connectors → Add custom connector
• LangChain Camden Tools Prompt/check_delivery pip install langchain-mcp-adapters

Other prompts on this server

• find_the_right_tool
• compare

Camden Tools also offers 7 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.