MCP ArchiMate Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARCHIMATE_MODEL_PATH | Yes | Path to the CoArchi model directory (e.g., /path/to/your/archimate/model) |
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 |
|---|---|
| get_model_summaryB | Get a summary of the ArchiMate model (element counts by layer and type) |
| list_elements_by_layerB | List all elements in a specific layer |
| search_elementsA | Search elements by name (case-insensitive) |
| get_elementA | Get details of a specific element by ID |
| list_available_element_typesA | List all available ArchiMate element types |
| list_relationship_typesA | List all available ArchiMate relationship types |
| create_elementB | Create a new ArchiMate element |
| create_relationshipB | Create a new ArchiMate relationship between two elements |
| create_diagramC | Create a new diagram/view |
| design_from_documentB | Generate ArchiMate model from an architecture markdown document |
| validate_modelB | Validate the ArchiMate model for errors |
| commit_and_pushA | Commit changes and push to git branch |
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 12 tools
Each tool has a clearly distinct purpose: creating elements/relationships/diagrams, committing changes, generating models from documents, retrieving elements, listing types, searching, and validating. No ambiguity between tools.
All tool names follow a consistent verb_noun snake_case pattern (e.g., create_element, list_elements_by_layer, validate_model), making it easy to predict functionality.
With 12 tools, the set is well-scoped for an ArchiMate modeling server, covering creation, retrieval, listing, validation, and documentation generation without being excessive or insufficient.
The tool set covers core operations (create, read, search, validate) but lacks update and delete for elements and relationships, which is a minor gap for full lifecycle management.