F
licenseNot graded
qualityD
maintenanceA comprehensive MCP server for managing product initiatives, architecture decisions, requirements, and releases, enabling AI tools to interact with architectural documentation and planning.
-
togaf10_EAP_MCP
Related Servers
Alternatives to togaf10_EAP_MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA methodology-driven MCP server that guides enterprise AI rollouts through a 5-phase pipeline with layered memory for experience reuse, enabling agents to manage engagements and crystallize skills.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that stores and queries shared company context, strategic spines, documents, and decision traces with citations and versioning.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceAn MCP server that provides a shared graph of an organization's projects, processes, areas, and principles, enabling consistent context for tools and AI agents.2Apache 2.0
- AlicenseAqualityAmaintenanceAn MCP server that lets AI agents build, validate, and export ArchiMate models using 45 tools, 9 resources, and 4 guided prompts.452GPL 3.0
- AlicenseAqualityAmaintenanceA read-only MCP server that gives AI agents access to Sparx Enterprise Architect models, enabling search, navigation, and reading of elements, packages, scenarios, and connectors from .qea exports without a running EA instance.1258 npmEuropean Union Public 1.2
TDQS
B3.4/5.0
Scored across 75 tools
Disambiguation3/5
Detailed descriptions help, but several tools have unclear boundaries: create_engagement vs start_engagement both create engagements, get_dashboard vs get_engagement vs start_here all surface current state, and risk_matrix vs diagram_risk_matrix cover similar matrices. The document pipeline (read_document, extract_from_document, ingest_document, summarize_document_for_architecture) and the assessment pair (assess_maturity, assess_readiness) also risk misselection without careful reading.
Naming Consistency3/5
Most tools use a readable snake_case verb-first pattern (get_engagement, diagram_capability_map, export_report), and families like diagram_*/export_* are consistent. However, a substantial minority are noun or phrase names (risk_matrix, capability_method, llm_status, about_knowledge, whats_new_for_me, start_here), so the overall convention is mixed rather than uniform.
Tool Count1/5
75 tools is far beyond the typical agent-selectable surface and falls in the extreme range. Many could be consolidated into parameterized tools—for example a single diagram tool with a type argument, or a single document-intake pipeline.
Completeness4/5
The surface is remarkably broad: ADM knowledge, engagement CRUD, capability/value-stream analysis, ArchiMate validation and export, security, roadmap, dashboards, and document intake are all covered. Minor gaps remain—notably no dedicated requirements register despite Requirements Management being central to ADM, and no generic deletion for risks, stakeholders, or actions.
Maintenance
ActivitySlowing
ResponsivenessNo issues