XMI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XMI_FILE_PATH | No | Path to the SysML XMI export file. Use this environment variable if the XMI file is in a custom location. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_packagesC | List all packages in the SysML model with optional filtering |
| get_packageB | Get detailed information about a specific package |
| find_classesC | Find classes/blocks by name, pattern, or package |
| get_class_detailsB | Get full details of a class including properties and inheritance |
| get_inheritance_hierarchyB | Get the inheritance chain for a class (parents and children) |
| list_enumerationsC | List all enumerations with optional filtering |
| get_enumerationB | Get details of an enumeration including all literals |
| search_documentationB | Full-text search across all documentation/comments |
| search_by_nameB | Search for any element by name across the entire model |
| resolve_referenceC | Resolve an xmi:id reference to get element details |
| get_model_statisticsB | Get statistics about the loaded SysML model |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose targeting specific SysML model elements or operations. For example, find_classes searches for classes by criteria, get_class_details retrieves detailed class information, and search_by_name performs broader element searches, with no significant overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case, such as find_classes, get_class_details, and list_packages. This uniformity makes the tool set predictable and easy to understand for an agent.
With 11 tools, the count is well-scoped for exploring and querying a SysML model. Each tool serves a specific purpose, such as retrieving details, listing elements, or searching, without redundancy, making the set comprehensive yet manageable.
The tool set covers key operations for SysML model exploration, including retrieval, listing, searching, and statistical analysis. Minor gaps might exist, such as tools for modifying or validating the model, but the provided tools support most agent workflows effectively without dead ends.