Federation in detail
Why MBEstudio is a game changer for AI-driven MBSE
MBEstudio is not a plugin or a requirements text generator. Its MCP server gives AI agents a structured workspace to read, change and check system engineering models, and nothing an agent writes reaches the model until a proposal is committed.
Multi-agent federation
Split the system. Give each subsystem to an agent.
Assign different subsystems to different agents, in Claude Code, Codex, Cursor, ChatGPT or any other MCP client. They can belong to different people. Each agent works from the same baseline and hands its work back to the studio as a model fragment.
1. Read the boundary
The agent asks for its subsystem and gets the boundary contracts, frozen interfaces, allocated functions, requirements and the baseline to generate against.
2. Submit a fragment
The agent stages its subsystem with its provenance. The model is not touched.
3. Reconcile in context
The studio places the fragment in the baseline, compiles the whole model and reports only what the fragment introduced, as one proposal.
Conflict reconciliation and guardrails
Agents propose. Engineers decide.
An agent cannot overwrite the system architecture. Every problem in a proposal comes back as a typed conflict with the resolutions it allows, and the model changes only when the proposal is committed.
| Conflict | What it catches | Your options |
|---|---|---|
| Interface mismatch | Port types, port directions, item types, units or rates that disagree across a connection between subsystems. | Accept, reject or replace |
| Frozen interface | A change to an interface definition, port or item on a boundary between subsystems. | Approve the interface change or reject |
| Allocation | A function left unallocated, or allocated more than once. | Accept, reject or replace |
| Traceability | A requirement with no satisfy or verify trace, reported as a warning. | Accept, reject or replace |
| Scope and ownership | Work that reaches outside the subsystem the agent was given, or into a subsystem someone else owns. | Accept or reject |
| Identity | An element that may be a rename or a match of an existing one, so stable IDs stay correct. | Match, accept the rename or keep as new |
| Model validity | Shape check failures and compile errors in the merged model. A compile error cannot be accepted. | Reject or replace; shape failures can also be accepted |
By default every conflict waits for review. A per model policy can settle the types you choose automatically. Each committed element keeps a stable ID and a record of the agent, model and baseline it came from.
Deep tool interoperability
Bridge code-driven engineering and the tools programs already run.
Send a subsystem and its dependencies into a chosen package. A dry run shows what will change first, and exporting again updates in place without duplicates. Edits made in the tool come back as a proposal, never as an overwrite.
SysML v2 API tools
Export to tools that serve the OMG SysML v2 API, check drift, and import their changes.
Cameo
Exchange XMI packages with Cameo. On the way back, elements are matched by name rather than by ID.
.sysml files
Plain text that sits in git and diffs like code. The SysML text stays the source of truth.
Current limit: a tool's change to a definition's own header is reported, not applied.
Simulation and behavioral execution
Beyond syntax: run what the model declares.
Behavior
Execute declared state machines, timers, guards and event traces, and see requirement verdicts over the run. Agents can start this with run_simulation.
Trade studies
Run NSGA-II trade studies against the model's stated objectives and constraints in the studio workspace. NSGA-II is not yet enabled through the agent worker; agents use run_trade_study for declared studies of up to 256 design points. No fluid solver, rigid-body solver or FMU execution is included.
Start
The federation tools are free on the MCP server.
https://studio.vectorstreamsystems.com/mcp
The tool reference and example shows the full sequence for one agent and one subsystem. In the studio, reconciliation and export are under File, Federation. To run this at scale, see Multi-Agent Federation.