get_job_status — MBEstudio MCP Tool Read-only
get_job_status
(get job status) is one of 32 tools on the
MBEstudio
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_job_status from your client
- Claude Code MBEstudio get_job_status run in your project directory
- Claude Desktop MBEstudio get_job_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MBEstudio get_job_status ~/.cursor/mcp.json
- VS Code MBEstudio get_job_status .vscode/mcp.json
- Zed MBEstudio get_job_status ~/.config/zed/settings.json
- Windsurf MBEstudio get_job_status ~/.codeium/windsurf/mcp_config.json
- Cline MBEstudio get_job_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MBEstudio get_job_status ~/.gemini/settings.json
- Grok MBEstudio get_job_status .mcp.json (in your project root)
- ChatGPT MBEstudio get_job_status Settings → Connectors → Advanced → Developer mode
- Claude.ai MBEstudio get_job_status Settings → Connectors → Add custom connector
- LangChain MBEstudio get_job_status 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_result
- cancel_job
- wait_for_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 14 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.