ArchiMate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARCHIMATE_AUDIT_LOG | No | Path to audit log file, or 'disabled' to disable audit logging. If not set, audit logging is disabled by default. |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| archimate_open_modelB | Open an ArchiMate model from a coArchi repository directory. Returns model metadata including element counts by layer. |
| archimate_save_modelB | Save the current model to disk |
| archimate_create_modelA | Create a new empty ArchiMate model with standard folder structure |
| archimate_list_elementsA | List elements in the model, optionally filtered by layer or type |
| archimate_get_elementB | Get detailed information about a specific element including its relationships |
| archimate_find_elementsA | Search for elements by name pattern (case-insensitive regex) |
| archimate_create_motivation_elementA | Create a Motivation layer element (Chapter 6). Use for stakeholders, goals, requirements, etc. |
| archimate_create_strategy_elementA | Create a Strategy layer element (Chapter 7). Use for capabilities, resources, and strategic planning. |
| archimate_create_business_elementB | Create a Business layer element (Chapter 8). Use for actors, processes, services, and business objects. |
| archimate_create_application_elementA | Create an Application layer element (Chapter 9). Use for application components, services, and data objects. |
| archimate_create_technology_elementB | Create a Technology layer element (Chapter 10). Use for nodes, devices, infrastructure, and physical elements. |
| archimate_create_implementation_elementA | Create an Implementation & Migration layer element (Chapter 12). Use for work packages, deliverables, and architecture plateaus. |
| archimate_create_composite_elementB | Create a composite element (Chapter 4). Use for grouping and locations. |
| archimate_create_relationshipB | Create a relationship between two elements. Validates against ArchiMate specification. |
| archimate_list_relationshipsA | List relationships, optionally filtered by element or type |
| archimate_get_valid_relationshipsB | Get valid relationship types between two element types (helps understand what connections are permitted) |
| archimate_list_viewsB | List all diagram views in the model |
| archimate_create_viewC | Create a new diagram view |
| archimate_add_to_viewA | Add an element to a diagram view. Connections for relationships between this element and any element already in the view are drawn automatically - you do not need to call archimate_add_connection_to_view for them. The response lists every connection that was auto-drawn in autoConnectedRelationships. |
| archimate_add_connection_to_viewA | Manually add a connection (line/arrow) between two diagram objects in a view. Normally unnecessary - archimate_add_to_view auto-draws connections for all relationships it finds between the new element and existing on-canvas elements. Use this tool only to: (a) restore a connection after calling archimate_add_to_view with auto_connect: false, or (b) add a connection that was not auto-drawn because one endpoint was not yet in the view. Both diagram objects must already be in the view. |
| archimate_update_elementC | Update an existing element |
| archimate_delete_elementB | Delete an element and its associated relationships |
| archimate_delete_relationshipC | Delete a relationship |
| archimate_layer_summaryB | Get a summary of elements by layer |
| archimate_impact_analysisB | Analyze dependencies and impact of an element |
| archimate_import_exchangeB | Import an ArchiMate model from Open Exchange Format XML file |
| archimate_export_exchangeB | Export the current model to ArchiMate Open Exchange Format XML |
| archimate_export_mermaidA | Generate Mermaid diagram syntax from the model or a specific view |
| archimate_export_diagramC | Export a diagram view as SVG or PNG image |
| archimate_export_markdownB | Export the model as Markdown documentation |
| archimate_export_html_deckA | Export the model as an interactive HTML deck with tabs and search |
| archimate_configure_auditC | Configure audit logging for model operations |
| archimate_get_audit_logB | Read recent entries from the audit log |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ArchiMate Element Types | Catalog of all ArchiMate 3.2 element types by layer |
| ArchiMate Relationship Types | Catalog of all ArchiMate 3.2 relationship types |
| Current Model Summary | Summary of the currently loaded model |
TDQS
Scored across 33 tools
Each tool has a clearly distinct purpose. The only potential overlap is between archimate_add_to_view and archimate_add_connection_to_view, but their descriptions explicitly differentiate them, with the former auto-drawing connections and the latter for manual addition.
All tools follow the 'archimate_verb_noun' pattern in snake_case, with verbs like create, delete, list, get, export, import, etc. The naming is highly consistent and predictable.
33 tools is on the higher side but still reasonable given the breadth of ArchiMate modeling (multiple layers, relationships, views, exports, audit, impact analysis). Each tool serves a specific purpose, and the count is not excessive.
The tool set covers creation, reading, updating, and deletion for most elements and relationships, as well as views, exports, imports, and analysis. Minor gaps exist: no tool to delete a view, and no update for relationships, but these are not critical.