design_status — METODIC MCP Tool
design_status
(design status) is one of 20 tools on the
METODIC
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call design_status from your client
- Claude Code METODIC design_status run in your project directory
- Claude Desktop METODIC design_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor METODIC design_status ~/.cursor/mcp.json
- VS Code METODIC design_status .vscode/mcp.json
- Zed METODIC design_status ~/.config/zed/settings.json
- Windsurf METODIC design_status ~/.codeium/windsurf/mcp_config.json
- Cline METODIC design_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI METODIC design_status ~/.gemini/settings.json
- Grok METODIC design_status .mcp.json (in your project root)
- ChatGPT METODIC design_status Settings → Connectors → Advanced → Developer mode
- Claude.ai METODIC design_status Settings → Connectors → Add custom connector
- LangChain METODIC design_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http metodic https://www.metodic.io/mcpOther tools on this server
- list_frameworks
- find_session_format
- answer_from_library
- search_articles
- search_methods
- design_session
- refine_session
- get_session
- session_one_pager
- generate_document
- list_my_sessions
- share_session
- get_credits
- add_debrief
- generate_worksheet
- generate_canvas
- generate_handout
- generate_slides
- generate_cards
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.