outdoor-kitchen-planning-guide — Outdoor Kitchen Designer MCP Resource
outdoor-kitchen-planning-guide
is one of 1 resource on the
Outdoor Kitchen Designer
MCP server. Connect the server and your client can attach it as context.
by client
How to attach outdoor-kitchen-planning-guide from your client
- Claude Code Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide run in your project directory
- Claude Desktop Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide ~/.cursor/mcp.json
- VS Code Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide .vscode/mcp.json
- Zed Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide ~/.config/zed/settings.json
- Windsurf Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide ~/.codeium/windsurf/mcp_config.json
- Cline Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide ~/.gemini/settings.json
- Grok Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide .mcp.json (in your project root)
- ChatGPT Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide Settings → Connectors → Advanced → Developer mode
- Claude.ai Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide Settings → Connectors → Add custom connector
- LangChain Outdoor Kitchen Designer Resource/outdoor-kitchen-planning-guide pip install langchain-mcp-adapters
Outdoor Kitchen Designer also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 6 October 2026.
A listing does not declare its resources, 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 resource's type and contents.