No user-submitted related servers found.
Scored across 9 tools
The facades have broadly overlapping exploration duties: search, nav, and structure all feel like code-navigation surfaces, and shared action names such as impact, overview, and knowledge appear in multiple tools. An agent would struggle to pick a tool without first querying action=help, since the boundary between facades is not clear from the names or action lists alone.
The eight codegraph facades follow a consistent lowercase single-word naming style (search, nav, structure, health, edit, project, index, viz), which is predictable across the set. The exceptions are the verb-noun set_project_path and the abbreviations nav/viz, which are minor deviations rather than a chaotic mix.
Nine tools is a well-scoped count for a code-intelligence suite: setup, indexing, searching, navigation, structural analysis, health, editing, project intelligence, and visualization each have a dedicated facade. Each tool bundles many actions but remains a single cohesive entry point, so the count feels intentional rather than excessive or thin.
The surface covers the full expected lifecycle for a code analyzer: project initialization, index management, code search, navigation, AST/structural analysis, health analysis, safe refactoring/editing, project metrics, and visualization. The edit facade even includes verification and mutation-probe actions, and health/test-gap covers quality checking, leaving no obvious dead end or missing major capability.