F
licenseNot graded
qualityA
maintenanceAn MCP server that gives an AI agent read and write access to a live SysML v2 model through the vendor-neutral OMG SysML v2 REST API.
2
-
Enterprise Architect MCP Server
by mm6502
Related Servers
Alternatives to Enterprise Architect MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to Sparx Systems Enterprise Architect repositories stored in various database systems via ODBC, allowing AI assistants to browse and query model data without requiring Windows or a running EA instance.MIT
- FlicenseAqualityCmaintenanceA read-only MCP server that gives AI coding agents structured access to a project's source code, architecture, documentation, and Git context through 16 tools for searching, reading, and comparing evidence without modifying files.16-
- FlicenseAqualityBmaintenanceA read-only MCP server that enables AI clients to search a knowledge base and retrieve complete source documents via narrow search and fetch tools.2-
- AlicenseNot gradedqualityAmaintenanceA deterministic, read-only MCP server that lets coding agents search Git-backed architecture decision records and retrieve decisions governing specific files. It includes rejected and superseded decisions, with no model, network, or write access.12Apache 2.0
- AlicenseBqualityDmaintenanceA read-only MCP server connecting AI assistants to Azure DevOps Server (on-premises) for browsing projects, repos, builds, work items, releases, pipelines, and test results.393931MIT
TDQS
A4.4/5.0
Scored across 12 tools
Disambiguation4/5
Most tools map cleanly to distinct actions and resources: get vs list vs search vs resolve are easy to separate, and the descriptions carefully explain each tool's role. The only real ambiguity is between ea_search and ea_search_and_any_of, which are near-duplicates differing only in how alternatives are applied, and ea_resolve can overlap with search in intent.
Naming Consistency5/5
All tools share the ea_ prefix and use snake_case with a consistent verb-first style: get_, list_, search_, and resolve. ea_search_and_any_of is the only name that breaks the simple verb_noun shape, but it is a coherent extension of the existing search name rather than a convention violation.
Tool Count5/5
Twelve tools is well within the ideal range and each tool serves a distinct read-only exploration workflow: navigation, element detail, search, diagrams, connectors, scenarios, schema, and model info. The count feels deliberate rather than bloated, and no tool appears redundant enough to remove.
Completeness4/5
The read-only Enterprise Architect model surface is well covered: package hierarchy, element details, search, relationship and diagram retrieval, scenarios, schema discovery, and model identity are all present. Minor gaps exist, such as package-level details beyond tree metadata and certain EA extension data like tagged values, but the core exploration workflows have no dead ends.
Maintenance
ActivityNo data
ResponsivenessNo issues