mbe_get_context — MBEstudio MCP Tool
mbe_get_context
(mbe get context) 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 mbe_get_context from your client
- Claude Code MBEstudio mbe_get_context run in your project directory
- Claude Desktop MBEstudio mbe_get_context ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MBEstudio mbe_get_context ~/.cursor/mcp.json
- VS Code MBEstudio mbe_get_context .vscode/mcp.json
- Zed MBEstudio mbe_get_context ~/.config/zed/settings.json
- Windsurf MBEstudio mbe_get_context ~/.codeium/windsurf/mcp_config.json
- Cline MBEstudio mbe_get_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MBEstudio mbe_get_context ~/.gemini/settings.json
- Grok MBEstudio mbe_get_context .mcp.json (in your project root)
- ChatGPT MBEstudio mbe_get_context Settings → Connectors → Advanced → Developer mode
- Claude.ai MBEstudio mbe_get_context Settings → Connectors → Add custom connector
- LangChain MBEstudio mbe_get_context 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_simulation
- 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_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.