synthesize_physical_solution — SkoIA Parts MCP Tool
synthesize_physical_solution
(synthesize physical solution) is one of 15 tools on the
SkoIA Parts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call synthesize_physical_solution from your client
- Claude Code SkoIA Parts synthesize_physical_solution run in your project directory
- Claude Desktop SkoIA Parts synthesize_physical_solution ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SkoIA Parts synthesize_physical_solution ~/.cursor/mcp.json
- VS Code SkoIA Parts synthesize_physical_solution .vscode/mcp.json
- Zed SkoIA Parts synthesize_physical_solution ~/.config/zed/settings.json
- Windsurf SkoIA Parts synthesize_physical_solution ~/.codeium/windsurf/mcp_config.json
- Cline SkoIA Parts synthesize_physical_solution ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SkoIA Parts synthesize_physical_solution ~/.gemini/settings.json
- Grok SkoIA Parts synthesize_physical_solution .mcp.json (in your project root)
- ChatGPT SkoIA Parts synthesize_physical_solution Settings → Connectors → Advanced → Developer mode
- Claude.ai SkoIA Parts synthesize_physical_solution Settings → Connectors → Add custom connector
- LangChain SkoIA Parts synthesize_physical_solution pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http skoia-parts https://parts.skoia.me/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.