Provides tools to commit and push model changes to a Git repository, enabling version control of ArchiMate models.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP ArchiMate Server Show me the API component"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server for ArchiMate/CoArchi model interaction. Works with VS Code Copilot, Cursor, and other MCP-compatible clients.
MCP ArchiMate Server enables AI assistants to read and write ArchiMate models stored in CoArchi XML format. Query elements, create relationships, design diagrams, and sync changes to Git—all through natural language.
Repository: https://github.com/dqxorg/mcp-archimate
Related MCP server: ArchiScribe MCP Server
Read and search ArchiMate models (CoArchi XML format)
Create elements, relationships, and diagrams
Generate models from architecture documentation
Auto-add visual connections to diagrams
Commit and push changes to Git branches
Full ArchiMate 3.2 schema support
1. Install via npm:
npm install -g archimate-chloe-mcp2. Add to VS Code settings (Ctrl+, → click {} icon):
{
"mcp": {
"servers": {
"archimate": {
"command": "archimate-chloe-mcp",
"env": {
"ARCHIMATE_MODEL_PATH": "/path/to/your/archimate/model"
}
}
}
}
}3. Restart VS Code
mcp add archimate -- archimate-chloe-mcpgit clone https://github.com/dqxorg/mcp-archimate.git
cd mcp-archimate
npm installThen add to VS Code settings:
{
"mcp": {
"servers": {
"archimate": {
"command": "node",
"args": ["/path/to/mcp-archimate/server.js"],
"env": {
"ARCHIMATE_MODEL_PATH": "/path/to/your/archimate/model"
}
}
}
}
}Set the ARCHIMATE_MODEL_PATH environment variable to your CoArchi model directory:
# Linux/Mac
export ARCHIMATE_MODEL_PATH=~/Documents/Archi/models/my-architecture
# Windows
set ARCHIMATE_MODEL_PATH=C:\Users\chloe\Documents\Archi\models\my-architecturepython -m archimate_mcp.servernode server.jsAfter installation, use the archimate-chloe-mcp command:
{
"mcp": {
"servers": {
"archimate": {
"command": "archimate-chloe-mcp",
"env": {
"ARCHIMATE_MODEL_PATH": "/path/to/your/archimate/model"
}
}
}
}
}Set ARCHIMATE_MODEL_PATH to your CoArchi model folder (the one with model/business/, model/application/, etc.).
Restart VS Code after adding the configuration.
Ask Copilot:
"What's in my application layer?"
"Show me all elements"
If you get a response, the MCP server is connected.
Tool | Description |
| Get model statistics by layer and type |
| List elements in business/application/technology layer |
| Search elements by name |
| Get element details by ID |
| Check model for errors |
Tool | Description |
| Create a new element |
| Create a relationship between elements |
| Create a new diagram/view |
| Add element to existing diagram |
| Add visual connection line |
| Auto-add all connections |
| Generate model from markdown |
| Git commit and push |
Tool | Description |
| List all ArchiMate element types |
| List all relationship types |
User: What's in my application layer?
→ Returns all application components and functions
User: Show me the API component
→ Returns element details with relationships
User: Create a BusinessActor for Product Owner
→ Creates new element in business layer
User: Connect the API to the Database with AccessRelationship
→ Creates relationship between elements
User: Add all connections to the C1 diagram
→ Adds visual connection lines for all relationships
User: Design from C:/docs/architecture.md
→ Generates full model from markdown documentBusinessActor, BusinessRole, BusinessCollaboration, BusinessProcess, BusinessFunction, BusinessService, BusinessObject
ApplicationComponent, ApplicationFunction, ApplicationService, DataObject
Node, Device, SystemSoftware, TechnologyService, Artifact
Type | Use Case |
| Service provided to actor |
| Data/control flow |
| Read/write data |
| Actor assigned to element |
| Implementation of specification |
| Strong whole-part |
| Whole-part |
| Event trigger |
The server expects a CoArchi model structure:
model-repository/
└── your-model/
└── model/
├── business/ # Business layer elements
├── application/ # Application layer elements
├── technology/ # Technology layer elements
├── relations/ # All relationships
└── diagrams/ # Views and diagramsThe commit_and_push tool automatically:
Stages all changes
Commits with your message
Creates a new branch (archi/{user}-{date})
Pushes to origin
Model not loading?
Verify ARCHIMATE_MODEL_PATH is set correctly
Check model has proper folder structure (model/business/, model/application/, etc.)
Connections not visible in diagram?
Use add_connections_from_relationships tool
Press F5 in CoArchi to reload
Element not found?
Use search_elements to find the correct ID
Check if element exists in the model
MIT
Add to your VS Code settings (settings.json):
{
"mcpServers": {
"archimate": {
"command": "python",
"args": ["-m", "archimate_mcp.server"],
"env": {
"ARCHIMATE_MODEL_PATH": "C:\\path\\to\\your\\archimate\\model"
}
}
}
}Add to claude_desktop_config.json:
{
"mcpServers": {
"archimate": {
"command": "python",
"args": ["-m", "archimate_mcp.server"],
"env": {
"ARCHIMATE_MODEL_PATH": "/path/to/your/archimate/model"
}
}
}
}# Create virtual environment
python -m venv .venv
# Activate
source .venv/Scripts/activate # Linux/Mac
.venv\Scripts\activate # Windows
# Install dependencies
pip install fastmcp
# Run tests
python -c "import sys; sys.path.insert(0, '.'); from archimate_mcp.server import get_model; m = get_model(); print(m.get_summary())"MIT License
Commit changes and push to git branch
Inputs: message, branch_name.
Create a new diagram/view
Inputs: diagram_name (required), element_ids.
Create a new ArchiMate element
Inputs: element_type (required), name (required), documentation.
Create a new ArchiMate relationship between two elements
Inputs: relationship_type (required), source_element_id (required), target_element_id (required), documentation.
Generate ArchiMate model from an architecture markdown document
Inputs: document_path (required), scope.
Get details of a specific element by ID
Inputs: element_id (required).
Get a summary of the ArchiMate model (element counts by layer and type)
Inputs: no named parameters.
List all available ArchiMate element types
Inputs: no named parameters.
List all elements in a specific layer
Inputs: layer (required).
List all available ArchiMate relationship types
Inputs: no named parameters.
Search elements by name (case-insensitive)
Inputs: query (required).
Validate the ArchiMate model for errors
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
AI Agent with Architectural Memory. Impact analysis (free), tests and code from the graph (pro).
Generate, edit, and export data-architecture diagrams from your AI. Column lineage, PNG in chat.
