Features
1. What Obeo AI for Capella Does
Obeo AI for Capella connects compatible AI assistants to a running Capella environment so engineers can explore, understand, analyze, modify, document, and verify architecture models.
The recommended workflow is:
Explore -> Understand -> Analyze -> Decide -> Modify -> Verify
2. What You Can Do
| Capability | What you can do | Example request |
|---|---|---|
Discover |
Find available Capella environments, projects, models, and diagrams. |
“Show me the projects and diagrams available in this workspace.” |
Understand |
Explore model structure, diagram contents, components, interfaces, dependencies, and existing documentation. |
“Explain the architecture around this component and its interfaces.” |
Analyze |
Assess change impacts, affected interactions, risks, and possible architecture improvements. |
“What would be affected if this component responsibility changed?” |
Modify |
Create projects, representations, model elements, relationships, and diagram content through controlled operations. |
“Add a logical component to this diagram and connect it to the existing system.” |
Document |
Read and update model or diagram documentation and maintain realization links. |
“Document this component’s responsibility and link it to the realized element.” |
Verify |
Refresh, arrange, inspect, and export diagrams so changes can be reviewed. |
“Refresh and arrange this diagram, then export it as a PNG for review.” |
3. Tool Reference
Most users can describe their goal directly to the AI assistant without choosing a tool themselves. This compact reference is intended for integrators and advanced users. The minimum profile is the least permissive server profile that publishes the tool. See the MCP reference for profile configuration, metadata, and detailed execution behavior.
Evolution note: The proposed tool surface and its classification concepts, including purpose, layer, intent, mutating behavior, profile, and batch execution, are expected to evolve in upcoming versions.
| Tool | Purpose | Minimum profile |
|---|---|---|
|
Return the embedded operating contract and Arcadia context for clients that cannot expose MCP resources to the model. |
|
|
List discoverable running automation environments. |
|
|
List projects in a selected workspace. |
|
|
Return model sessions, semantic roots, representations, and collaborative state. |
|
|
Create a Capella project in the selected workspace. |
|
|
List representation definitions compatible with a model context. |
|
|
List semantic owners for a selected representation definition. |
|
|
Discover representation definitions across a model session. |
|
|
Discover compatible semantic owners across a model session. |
|
|
Create, open, or close representations. |
|
|
Summarize model structure, architecture packages, and validation context. |
|
|
Describe diagram views and available creation and selection palette operations. |
|
|
List semantic elements accepted by a discovered palette selection tool. |
|
|
Read the active diagram or workspace selection. |
|
|
Set the active diagram or workspace selection. |
|
|
Execute discovered palette operations; prefer this route when newly created content must be visible in a diagram. |
|
|
List direct-child semantic creation actions for explicit semantic-only intent or diagram fallback. |
|
|
Execute one semantic creation action without creating or guaranteeing a diagram view. |
|
|
Return semantic references and affected representations for an element. |
|
|
Arrange, refresh, export, or rename content in diagrams. |
|
|
Read documentation stored on a diagram. |
|
|
Replace documentation stored on a diagram. |
|
|
Arrange an open Capella diagram with optimized ELK layout. |
|
|
Attach realization links through ordered Capella edit steps. |
|
|
Read documentation from the selected Capella element. |
|
|
Update documentation on the selected Capella element. |
|
|
Resolve the typed component behind a Capella |
|
|
Query one specific missing fact that dedicated inspection does not expose, or run explicitly requested read-only AQL. |
|
|
Inspect EMF types, filtered properties and typed references; navigate session roots and direct containment. |
|
|
Create Ecore metamodel elements or edit writable features of existing Capella elements. |
|
Prefer Capella or Sirius tools for Capella model changes; use direct feature edits only when those tools do not express the requested change.
4. Legacy Tools
The following older tools remain available for compatibility. Legacy tools are available only under edit; they are not guaranteed to leave data unchanged. New workflows should use the recommended alternatives.
| Legacy tool | Recommended alternative |
|---|---|
|
Use |
|
Use |
|
Use |
|
Use |
|
Use |
|
Use |
|
Use |
|
Use |
|
Use |
|
Use |
|
Use |
5. Multi-Step Operations
When an operation contains several steps, execution stops at the first error. For operations that change the model, completed changes remain applied and are not automatically rolled back. See the MCP reference for detailed retry and execution guidance.
6. Deployment and Compatibility
The following client and transport combinations have been tried. This list is not an exhaustive compatibility guarantee.
| Transport | Clients tried |
|---|---|
HTTP |
Codex CLI; Gemini CLI (Enterprise/API); Qodo IDE plugin; Kiro IDE |
stdio |
ChatGPT desktop app / Codex CLI; Claude Code / Claude Desktop; Antigravity IDE; VS Code Chat on Windows |
For client setup examples, see LLM Client Configuration.
The available trial records did not distinguish between the listed Codex or Claude surfaces for stdio. Check the exact surface before treating either stdio entry as a surface-specific compatibility guarantee.
The default transport is stdio. Local HTTP binds to 127.0.0.1 by default. Remote plain HTTP is rejected; remote HTTPS requires a bearer token. The server also supports allowed-origin and allowed-host restrictions.
The MCP and CLI tools require Java 21, included with standard Capella 7.1.0. Installation targets Capella 7.1.0 and also supports 7.0.1 and 6.1.0 on Windows, Linux, and macOS. Older Capella versions and SMW distributions without a bundled Java 21 need a separate Java 21 for these tools; see the Java setup instructions.
Local deployment does not guarantee that model data remains on the local machine: the configured AI client or model provider determines what context is sent outside the environment.
7. Demonstration Scenarios
-
The Airport Turnaround acceptance scenario exercises representation and diagram operations together with Capella inspection and analysis.
-
The IFE USB integration scenario covers component understanding, impact analysis, architecture evolution, model editing, verification, and option comparison.
-
Diagram scenarios demonstrate arrangement and PNG export as reusable evidence.