sim_bind — whatif MCP Tool
sim_bind
(sim bind) is one of 46 tools on the
whatif
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call sim_bind from your client
- Claude Code whatif sim_bind run in your project directory
- Claude Desktop whatif sim_bind ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor whatif sim_bind ~/.cursor/mcp.json
- VS Code whatif sim_bind .vscode/mcp.json
- Zed whatif sim_bind ~/.config/zed/settings.json
- Windsurf whatif sim_bind ~/.codeium/windsurf/mcp_config.json
- Cline whatif sim_bind ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI whatif sim_bind ~/.gemini/settings.json
- Grok whatif sim_bind .mcp.json (in your project root)
- ChatGPT whatif sim_bind Settings → Connectors → Advanced → Developer mode
- Claude.ai whatif sim_bind Settings → Connectors → Add custom connector
- LangChain whatif sim_bind pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http whatif https://sim.pflow.xyz/mcpOther tools on this server
- sim_calibrate
- sim_canonical
- sim_classify
- sim_code_to_flow
- sim_compare
- sim_components
- sim_compose
- sim_conformance
- sim_create_collection
- sim_create_model
- sim_crosscheck
- sim_dataset
- sim_delete_model
- sim_diagnose
- sim_diff
- sim_distill
- sim_edges
- sim_evaluate
- sim_extend
- sim_get_binding
- sim_get_model
- sim_invariants
- sim_license_model
- sim_link
- sim_list_bindings
- sim_list_models
- sim_map_get
- sim_map_list
- sim_map_put
- sim_my_sheets
- sim_neighbors
- sim_optimize
- sim_param_heatmap
- sim_prompt
- sim_propose_types
- sim_publish
- sim_publish_app
- sim_publish_compare
- sim_receipt
- sim_refine
- sim_reroll
- sim_run_pipeline
- sim_scenario
- sim_supersede_model
- sim_verify
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.