plan-and-execute — plith MCP Prompt

plan-and-execute is one of 6 prompts on the plith MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke plan-and-execute from your client

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

Other prompts on this server

• try-rigor-free
• agent-preflight
• cost-aware-execution
• output-validation
• setup-guardrails

plith also offers 6 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.