• Home
  • MCP (Model Context Protocol) Server for Enterprise Architect

MCP (Model Context Protocol) Server for Enterprise Architect

Short Demo of the Server Features


(3m56s, with voice)

System Requirements

  • Microsoft® Windows 11 and Windows 10 64-bit (x64)
    • Linux and macOS are currently not supported
  • Microsoft .NET Desktop Runtime 9.0.5 or later
  • Microsoft .NET Framework 4.7.2 or later
  • Enterprise Architect 17.0 or later, 64-bit (x64) version
    (The 32-bit version and/or older versions of Enterprise Architect may be used but have not been tested or guaranteed to work well.)
  • Currently tested only for qea/qeax files
  • Tested with the Claude for Windows desktop application, version 0.9.3

Connect to MCP Client

First, you need to set up a connection to the MCP client. In this guide, the MCP Client is the Claude for Windows desktop application. The following steps are the initial steps to confirm that it works well.

  1. Confirm that the 64-bit version of Enterprise Architect works well.
  2. Install .NET Desktop Runtime 9.0.5 or a later version if it is not already installed.
  3. Install the MCP Server for Enterprise Architect; you can download the installer from the link below.
  4. Launch the Claude application, then select the menu at the top left. Select "File" > "Settings...".
  5. Select the "Developer" group, then press the "Edit Config" button. Open the "claude_desktop_config.json" file with your preferred text editor.
  6. Add information about the MCP Server. You can find an example below.
  7. Restart the Claude application and check for errors related to the MCP Server.
    (With the initial settings, the Claude application continues to run when you close the window. Stop the process or log off from the Windows session.)
  8. Confirm that you can see the tools related to the MCP server.
  9. Launch Enterprise Architect, open a project, and then open a diagram.
  10. In Claude, ask, for example, "Give me a summary of the current diagram." Claude will show confirmation dialogs to connect to the MCP Server (for first call of every tool). Allow all of them.
  11. You can view information related to the current diagram in Enterprise Architect.

Sparx Systems Japan cannot provide support for any setup issues except those strictly related to our MCP Server and Add-in.

Example of claude_desktop_config.json

If you don't have any other MCP Servers, copy and paste the following into the file. If you do, only add the "Enterprise Architect" part. Change this if the Enterprise Architect installation directory is different from the default path.

{
  "globalShortcut": "",

  "mcpServers": {
    "Enterprise Architect": {
      "command": "C:\\Program Files\\Sparx Systems\\EA\\MCP_Server\\MCP3.exe"
    }
  }
}

Log Files

The Claude application outputs the log file to %APPDATA%\Claude\logs\mcp-server-Enterprise Architect.log. The MCP add-in outputs the error log to %APPDATA%\Sparx Systems\EA\MCP_EA.log. These files are useful for solving issues. If you believe the issues are related to the MCP Server for Enterprise Architect, please send us these two files.

MCP Server Features

The MCP Server offers the following tools. You do not specify which tools are used; your LLM automatically selects the appropriate ones.

There are some interactive tools that work with Enterprise Architect. With these tools, you can open diagrams, select elements in diagrams, and select elements in the Browser window from MCP client.

There are no tools for updating models, adding new elements, etc. We think that we cannot currently avoid the unintended, disruptive changes caused by AI, especially the deletion of models.

  • Diagrams:
    • get_current_diagram
    • get_diagram
    • open_diagram - open a diagram in Enterprise Architect
    • get_elements_used_in_diagram - all elements on the diagram
    • get_connectors_used_in_diagram - all connectors on the diagram
  • Elements:
    • get_current_element
    • get_element
    • select_element_in_browser
    • select_element_in_diagram
    • get_child_diagrams
    • get_child_elements
    • get_connectors
    • get_attributes - both attributes and tagged values
    • get_operations - currently, no parameters information
    • find_in_diagrams - find all diagrams which the target element is used
    • find_elements_by_name - support exact match or including the text for names
  • Packages:
    • get_root_packages
    • get_package
    • select_package_in_browser
    • get_diagrams_in_package
    • get_elements_in_package
    • get_packages_in_package
  • Others:
    • clear_internal_cache - need to request if you modify the model

Current Limitations

  • The returned elements, diagrams, etc. have limited properties.
  • Messages in Sequence diagrams and Communication diagrams are not supported. It is very difficult to return all messages with the Fragments and their conditions.
  • When two or more Enterprise Architect instances run, the MCP Server connects with the first instance of Enterprise Architect process.

Structure of the MCP Server

The MCP Server for Enterprise Architect has two components: MCP3.exe and MCP_EA.dll. MCP3.exe is an MCP Server executable, and MCP clients can connect using the "STDIO" method. MCP3.exe is built with .NET 9.0. MCP_EA.dll is a standard Enterprise Architect add-in that works within the Enterprise Architect process. The two processes communicate via the Named Pipe.


(This image was created using LLM.)

There is no plan to offer an HTTP-based MCP server for Enterprise Architect, as doing so could violate the Enterprise Architect EULA.

The MCP Add-in (MCP_EA.dll) loads some locally installed .NET Framework library files. This may affect the behavior of other .NET Framework-based add-ins.

FAQ: Why is it MCP3.exe and not MCP.exe? (or What does the 3 mean?) - I failed twice before creating the latest MCP Server. :-)

Download Installer

We do not guarantee proper operation of the MCP Server and are under no obligation to provide support. This installer is only available if you agree to the terms.

MCP_EA.msi
(Latest release: Version 1.2 on 2 June 2025)

Important Note:
If the installation process ends without any files being installed, you need to install .NET Desktop Runtime 9.0.5 or a later version.

Questions, Bug Reports and Feature Requests

You may submit questions, bug reports, and feature requests via our inquiry form, or email us at global@sparxsystems.jp.

While we will do our best to provide support and add new features and bug fixes, we are under no obligation to do so.