run_simulation — MBEstudio MCP Tool Mutating
run_simulation
(run simulation) is one of 31 tools on the
MBEstudio
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_simulation from your client
- Claude Code MBEstudio run_simulation run in your project directory
- Claude Desktop MBEstudio run_simulation ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MBEstudio run_simulation ~/.cursor/mcp.json
- VS Code MBEstudio run_simulation .vscode/mcp.json
- Zed MBEstudio run_simulation ~/.config/zed/settings.json
- Windsurf MBEstudio run_simulation ~/.codeium/windsurf/mcp_config.json
- Cline MBEstudio run_simulation ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MBEstudio run_simulation ~/.gemini/settings.json
- Grok MBEstudio run_simulation .mcp.json (in your project root)
- ChatGPT MBEstudio run_simulation Settings → Connectors → Advanced → Developer mode
- Claude.ai MBEstudio run_simulation Settings → Connectors → Add custom connector
- LangChain MBEstudio run_simulation pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mbestudio https://studio.vectorstreamsystems.com/mcpOther tools on this server
- describe_mbestudio
- get_credit_balance
- estimate_cost
- generate_system_model
- build_3d_model
- run_trade_study
- verify_model
- export_model
- build_full_system
- run_agent_swarm
- reprompt_agent
- generate_safety_analysis
- get_job_status
- get_job_result
- cancel_job
- mbe_list_subsystems
- mbe_get_context
- mbe_submit_fragment
- mbe_reconcile
- mbe_list_conflicts
- mbe_resolve_conflict
- mbe_commit
- mbe_list_targets
- mbe_add_target
- mbe_list_packages
- mbe_export
- mbe_import_from
- mbe_drift
- mbe_create_baseline
- mbe_diff
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.