ArchiMate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_archimate_diagramB | Generate ArchiMate diagrams in Mermaid or Draw.io format from elements and relationships |
| validate_archimate_modelC | Validate ArchiMate elements and relationships against the ArchiMate 3.2 specification |
| list_archimate_elementsB | List all available ArchiMate 3.2 element types with their layers |
| list_archimate_relationshipsB | List all available ArchiMate relationship types |
| export_archimate_xmlC | Export ArchiMate model as standard XML Open Exchange Format (.archimate) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-business-model | Create a business layer ArchiMate model with guided steps for a specific domain |
| validate-and-fix | Validate ArchiMate model and provide specific suggestions for fixing violations |
| suggest-architecture-pattern | Suggest appropriate ArchiMate architecture patterns based on requirements |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| archimate-elements | Complete ArchiMate 3.2 element reference with descriptions, usage guidance, and examples |
| archimate-relationships | ArchiMate relationship types, rules, validation matrix, and best practices |
| model-templates | ArchiMate model templates, common patterns, and domain-specific examples |
| quick-reference | Quick reference guide for ArchiMate modeling with common patterns and anti-patterns |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: exporting XML, generating diagrams, listing elements, listing relationships, and validating models. An agent can easily distinguish between these operations as they target different aspects of ArchiMate model management.
All tool names follow a consistent verb_noun pattern with 'archimate' as a common prefix (e.g., export_archimate_xml, list_archimate_elements). This predictable naming scheme makes the tool set easy to navigate and understand.
With 5 tools, this server is well-scoped for its purpose of ArchiMate model handling. Each tool earns its place by covering essential operations like export, diagram generation, listing, and validation, without being overly sparse or bloated.
The tool set covers key aspects of ArchiMate model interaction, including export, visualization, information retrieval, and validation. A minor gap exists in CRUD operations for creating or modifying models, but agents can likely work around this by using external tools or focusing on analysis and export tasks.