mcp-archimate
Related Servers
Alternatives to mcp-archimate
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows AI agents to manage BuildBase resources (users, workspaces, subscriptions, projects) via 48 tools, with built-in agent authentication and discovery.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to manage STAR-pattern architecture diagrams, creating, updating, listing, and building interactive viewers via tool calls.MIT
- FlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for managing product initiatives, architecture decisions, requirements, and releases, enabling AI tools to interact with architectural documentation and planning.-
- FlicenseNot gradedqualityAmaintenanceAn 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-
- FlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to interact with Azure DevOps projects, work items, repositories, pipelines, wikis, and more via 21 tools.21-
- AlicenseNot gradedqualityAmaintenanceMCP server that provides 25 tools for AI agents to query and modify a dependency graph, enabling impact analysis and provenance tracking for AI-assisted development.8MIT
TDQS
Scored across 45 tools
Most tools have clearly distinct purposes, such as 'add_element' vs 'add_relationship' vs 'add_node_to_view'. However, there is some overlap between 'export_model_content' and 'export_model_to_file', and between 'validate_model' and 'validate_semantics', though descriptions help differentiate them.
Tool names use a mix of verbs like 'add', 'create', 'update', 'delete', 'export', 'load', 'query', 'validate', etc. Without a consistent verb_noun pattern, but the names are still descriptive and readable.
At 45 tools, the count is high but justifiable given the complexity of ArchiMate modeling, covering CRUD for multiple entity types, validation, layout, and reporting. However, some redundancy exists with batch operations and similar query tools.
The tool set covers core model lifecycle: creation, editing, deletion, validation, export, and layout. Notable gaps include lack of update/delete for notes and limited folder management, but overall domain coverage is strong.