Enterprise Architect MCP server

Enterprise Architect MCP Server

A read-only Model Context Protocol (MCP) server for Sparx Enterprise Architect .qea exports. Gives AI agents access to EA analysis models — search elements, navigate packages, read use case scenarios, and traverse connectors — without a running EA instance.

Works with any MCP client (VS Code / GitHub Copilot, Claude Desktop, Cursor, Windsurf). Reads the .qea SQLite export directly, never writes to it, and every response carries completeness metadata so an agent can tell a truncated answer from a complete one.

Keywords: MCP server · Sparx Enterprise Architect · .qea · UML · use case scenarios · package tree · connectors · diagrams · model search · AI agent tooling

Prerequisites

• Node.js 22+ (uses the built-in node:sqlite module)
• A .qea file exported from Sparx Enterprise Architect

Installation

VS Code / GitHub Copilot

The quickest route is the Install in VS Code badge at the top of this page. There is nothing to fill in: the server asks for your .qea path the first time an agent queries the model, and remembers the answer for next time.

To register it from a terminal instead, which is handier for scripting or a shared setup, use one CLI call:

code --add-mcp '{\"name\":\"enterprise-architect\",\"command\":\"npx\",\"args\":[\"-y\",\"enterprise-architect-mcp\"]}'

The \" sequences are for the code shim, which re-parses the argument after PowerShell has already handed it over — escaping with PowerShell's own backtick, or using --%, still arrives with the quotes stripped. The single quotes stop PowerShell from touching the string. On bash or zsh the plain form works instead:

code --add-mcp '{"name":"enterprise-architect","command":"npx","args":["-y","enterprise-architect-mcp"]}'

To configure it by hand instead, add to your project's .vscode/mcp.json:

{
  "servers": {
    "enterprise-architect": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "enterprise-architect-mcp"]
    }
  }
}

Nothing personal is in that file, so it can be committed as-is and each developer answers the prompt once on their own machine. If you would rather not be asked at all, name the path up front — as a trailing argument, in an env block, or in a gitignored .env in your workspace root:

EA_QEA_PATH=C:\EA\exports\model.qea

Claude Desktop

The same path-less configuration goes in claudedesktopconfig.json (%APPDATA%\Claude\ on Windows, ~/Library/Application Support/Claude/ on macOS):

Shortened. The full README is on GitHub.