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