Skip to main content
Glama

Related Servers

Alternatives to repo2graph

  • A
    license
    B
    quality
    A
    maintenance
    An MCP code-intelligence server for AI agents with pre-indexed AST cache, 62 MCP tools, and TOON-compressed output, enabling token-efficient code analysis and project health grading entirely locally.
    9
    54
    MIT

Related Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables coding agents to query a local-first code intelligence graph of Python repositories—covering functions, classes, modules, and their relationships—via MCP, supporting subgraph retrieval, caller lookup, and impact analysis without re-reading the codebase.
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables coding agents to query a local, multi-repo code graph for symbol exploration, blast radius analysis, co-change mining, and durable code-anchored memory via MCP tools.
    153 npm
    14
    Business Source 1.1
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI coding agents to navigate and understand entire codebases through symbol-aware semantic retrieval and relational call graph traversal, supporting structural impact analysis and code modification workflows over MCP.
    Apache 2.0
  • F
    license
    Not graded
    quality
    A
    maintenance
    Enables agents to build and query code knowledge graphs for repositories in a folder — finding shortest paths between concepts, explaining concepts with neighbours and community context, and visualizing per-repo graphs through MCP tools.
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI coding agents to query a semantic code graph over MCP, retrieving exact function source, definitions, callers/callees, impact analysis, and minimal test selection instead of whole files.
    14
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables LLM agents to query a codebase's structural knowledge (symbols, imports, call graphs, etc.) via MCP, reducing tokens and improving correctness compared to raw file access.
    583 npm
    7
    MIT

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct resource+action, and the descriptions explicitly cross-reference siblings (repo_search vs repo_neighbours vs repo_map; one-hop neighbours vs multi-hop repo_path_between vs reverse repo_blast_radius). Overlapping graph-traversal tools are cleanly separated by their 'When NOT to use' clauses, leaving no realistic misselection.

Naming Consistency5/5

Every tool uses the same repo_ prefix with a consistent snake_case noun/verb phrase (repo_map, repo_search, repo_find_symbol, repo_blast_radius). No camelCase or verb-style mixing.

Tool Count5/5

Nine tools is well-scoped for a read-only code-graph service: layout, search, symbol lookup, read, and several traversal/analysis operations, plus two diagnostics. Each tool earns its place and none is redundant.

Completeness4/5

Coverage of the read-only query lifecycle is strong: map, search, symbol resolution, read, neighbours, path-finding, and blast radius. Minor gaps remain — no tool to initiate an index build (only repo_build_status to poll) and no direct file/listing operation — but these are workable for the stated purpose.

Maintenance

ActivityActive
ResponsivenessWithin a week