launch_plan — AgentoolRank MCP Prompt
launch_plan
is one of 3 prompts on the
AgentoolRank
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke launch_plan from your client
- Claude Code AgentoolRank Prompt/launch_plan run in your project directory
- Claude Desktop AgentoolRank Prompt/launch_plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentoolRank Prompt/launch_plan ~/.cursor/mcp.json
- VS Code AgentoolRank Prompt/launch_plan .vscode/mcp.json
- Zed AgentoolRank Prompt/launch_plan ~/.config/zed/settings.json
- Windsurf AgentoolRank Prompt/launch_plan ~/.codeium/windsurf/mcp_config.json
- Cline AgentoolRank Prompt/launch_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentoolRank Prompt/launch_plan ~/.gemini/settings.json
- Grok AgentoolRank Prompt/launch_plan .mcp.json (in your project root)
- ChatGPT AgentoolRank Prompt/launch_plan Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentoolRank Prompt/launch_plan Settings → Connectors → Add custom connector
- LangChain AgentoolRank Prompt/launch_plan pip install langchain-mcp-adapters
Other prompts on this server
AgentoolRank also offers 2 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 7 October 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.