MMI Architecture Analyzer
Related Servers
Alternatives to MMI Architecture Analyzer
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for automated architectural mapping, security vulnerability detection, ML asset tracking, and code metrics in local repositories.-
- AlicenseNot gradedqualityBmaintenanceMCP server that provides tools for architecture analysis, risk diagnosis, quality metrics, and regression guarding to support AI-driven code review and incremental refactoring workflows.5MIT
- AlicenseAqualityAmaintenanceAn MCP server that maps any repository into architecture diagrams, providing tools for scanning code facts, building import graphs, and generating Mermaid/DOT diagrams, plus architecture rule enforcement for CI.531 npm1MIT
- FlicenseAqualityBmaintenanceMCP server for repository mapping, dependency analysis, and architecture diagram generation for JavaScript, TypeScript, and Python projects.48 npm-
- AlicenseAqualityDmaintenanceMCP server for comprehensive code analysis, navigation, and quality assessment across 25+ programming languages.988MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that provides Sonar-grade static analysis (bugs, vulnerabilities, code smells) for TypeScript/JS and C# repositories, with CLI and dashboard support.MIT
TDQS
Scored across 9 tools
Most tools have distinct purposes, such as analyze_abstraction for abstraction levels and analyze_cycles for circular dependencies, but analyze_mmi overlaps by running multiple analyses that other tools handle individually, which could cause confusion in tool selection. The monitoring tools (get_monitoring_status, start_monitoring, stop_monitoring) are clearly separate from analysis tools, reducing overall ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case, such as analyze_abstraction, get_monitoring_status, and visualize_architecture. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions across the nine tools.
With 9 tools, the count is well-scoped for an architecture analyzer server, covering analysis, monitoring, and visualization aspects without being overwhelming. Each tool serves a clear role, such as specific analyses or monitoring controls, making the set appropriately sized for the domain.
The tool set provides comprehensive coverage for architecture analysis, including specific checks (e.g., layering, encapsulation), overall scoring (analyze_mmi), monitoring lifecycle (start/stop/get status), and visualization. A minor gap is the lack of tools for fixing or suggesting corrections for identified violations, but agents can work around this by using analysis results to guide manual improvements.