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