plan_build — catalog MCP Prompt

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

by client

How to invoke plan_build from your client

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

Other prompts on this server

• compare_for_project
• verify_provenance

catalog also offers 5 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.