plan_verification_waterfall — WarmInboxes Free MCP: Fleet Planner MCP Tool
plan_verification_waterfall
(plan verification waterfall) is one of 16 tools on the
WarmInboxes Free MCP: Fleet Planner
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call plan_verification_waterfall from your client
- Claude Code WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall run in your project directory
- Claude Desktop WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall ~/.cursor/mcp.json
- VS Code WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall .vscode/mcp.json
- Zed WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall ~/.config/zed/settings.json
- Windsurf WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall ~/.codeium/windsurf/mcp_config.json
- Cline WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall ~/.gemini/settings.json
- Grok WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall .mcp.json (in your project root)
- ChatGPT WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall Settings → Connectors → Advanced → Developer mode
- Claude.ai WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall Settings → Connectors → Add custom connector
- LangChain WarmInboxes Free MCP: Fleet Planner plan_verification_waterfall pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fleet-planner https://warminboxes.com/mcp/planner
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.