archimate-mcp¶
A self-contained ArchiMate model engine exposed as an MCP server and A2A agent — full ArchiMate 3.x authoring for AI agents, with round-trip Open Group Model Exchange File Format so models open directly in Archi.
Official documentation
This site is the canonical reference for archimate-mcp, maintained alongside
every release.
Overview¶
archimate-mcp gives AI agents the full ArchiMate 3.x authoring surface through
typed, deterministic MCP tools. Archi has no native server API, so this package
ships its own dependency-light engine built on the Python standard library
(xml.etree.ElementTree). It provides:
ArchiApi— a stateful façade over a single ArchiMate model file: model lifecycle, full CRUD on elements, relationships, folders, and views (diagrams), query/traversal, and Open Exchange Format import/export.- Six MCP tools —
archi_model,archi_element,archi_relationship,archi_view,archi_folder, andarchi_query, spanning the complete ArchiMate vocabulary (Strategy, Business, Application, Technology, Physical, Motivation, and Implementation layers) with structural validation. - An A2A agent server — the
archimate-agentconsole script wraps the same tool surface as a Pydantic-AI agent for graph-orchestrated workflows.
Models authored through archimate-mcp round-trip the Open Group Model Exchange
File Format, so they open directly in Archi and any conformant ArchiMate tool.
Explore the documentation¶
- Installation — pip, source, extras, and the prebuilt Docker image.
- Deployment — run the MCP and agent servers, Docker Compose, Caddy + Technitium.
- Usage — the MCP tools, the
ArchiApiclient, and the CLI entry points. - Overview — the model engine, layered façade, and MCP/A2A surface.
- Concepts — the
CONCEPT:ARCHI-*registry.
Quick start¶
Point it at a working model file and run an HTTP server:
See Installation and Deployment for the full matrix (PyPI extras, Docker image, all transports, the A2A agent server, reverse proxy, and DNS).