Archy
Related Servers
Alternatives to Archy
- AlicenseAqualityDmaintenanceEnables AI assistants to review GitLab merge requests by fetching changes, analyzing diffs, adding comments, and managing approvals through the GitLab API. Supports complete merge request analysis, file-specific reviews, and version comparisons.124MIT
- AlicenseBqualityDmaintenanceA code review tool server based on Model Context Protocol (MCP), providing multi-dimensional code review and scoring functions.42Apache 2.0
Related Servers
- AlicenseNot gradedqualityCmaintenanceFramework-agnostic architecture-rule enforcement for AI agents: analyzes Python codebases import graphs against declarative rulesets to report layer, forbidden-import, and cycle violations with file and line numbers. Supports MCP, OpenAI, Anthropic, LangChain, LlamaIndex, and CLI integrations.MIT
- AlicenseNot gradedqualityAmaintenanceServes the architectural graph of a hexagonal-architecture codebase to coding agents via stdio, providing tools to analyze dependencies, check violations, and inspect structural changes.5 npmMIT
- AlicenseAqualityBmaintenanceProvides read-only structural analysis of codebases, surfacing architecture smells with traffic-light ratings and rendering dependency relationships as Mermaid flowcharts.4MIT
- FlicenseNot gradedqualityBmaintenanceEnables coding agents to analyze Python source with AST-based static analysis, detect circular dependencies across monorepo packages via Tarjan SCC, and produce a topological build order with Kahn's algorithm along with refactoring plans and graph metrics. Runs with zero external dependencies over MCP from Claude Desktop, Cursor, or any compliant client.7-
- AlicenseNot gradedqualityCmaintenanceFast architectural linter & guardrail engine for AI coding agents. Detects layer violations, leaked secrets, and enforces .cursorrules & CLAUDE.md standards in ~12ms.438 npm5MIT
- FlicenseNot gradedqualityBmaintenanceEnables coding agents to run deterministic, zero-dependency AST static analysis over source code, building call graphs and dependency metrics to find orphaned functions, unreachable methods, breaking API surface diffs, and token-bloat clusters, then return a structured refactoring plan. It plugs into MCP clients like Claude Desktop, Cursor, and Windsurf via a single Python entrypoint.7-
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: archy_check catches direct layer violations, archy_contracts handles transitive contract rules, archy_cycles finds import cycles, archy_graph dumps the full dependency graph, archy_high_risk_modules ranks high-risk modules, archy_impact computes blast radius, and archy_trend reads history. No two tools overlap in functionality.
All tools follow the consistent pattern 'archy_' followed by a descriptive noun (check, contracts, cycles, graph, high_risk_modules, impact, trend). Conventions are uniform across the set.
With 7 tools, the server is well-scoped for Python architecture analysis. Each tool addresses a specific need—violations, contracts, cycles, graph, risk, impact, and trends—without being too few or excessive.
The tool set covers core analysis tasks (direct/transitive violations, cycles, full graph, risk, impact, and trends). Minor gaps: tools like archy_graph_focus or archy_graph_summary are mentioned but not provided as separate tools, and there is no tool for listing architecture rules or configuration. Still, the main workflows are well-supported.