explore_design_conditions — epwforge mcp MCP Tool
explore_design_conditions
(explore design conditions) is one of 6 tools on the
epwforge mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call explore_design_conditions from your client
- Claude Code epwforge mcp explore_design_conditions run in your project directory
- Claude Desktop epwforge mcp explore_design_conditions ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor epwforge mcp explore_design_conditions ~/.cursor/mcp.json
- VS Code epwforge mcp explore_design_conditions .vscode/mcp.json
- Zed epwforge mcp explore_design_conditions ~/.config/zed/settings.json
- Windsurf epwforge mcp explore_design_conditions ~/.codeium/windsurf/mcp_config.json
- Cline epwforge mcp explore_design_conditions ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI epwforge mcp explore_design_conditions ~/.gemini/settings.json
- Grok epwforge mcp explore_design_conditions .mcp.json (in your project root)
- ChatGPT epwforge mcp explore_design_conditions Settings → Connectors → Advanced → Developer mode
- Claude.ai epwforge mcp explore_design_conditions Settings → Connectors → Add custom connector
- LangChain epwforge mcp explore_design_conditions pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http epwforge-mcp https://epwforge.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.