Skip to main content
Glama

Related Servers

Alternatives to Cartograph

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for local-first code intelligence, providing structural code graph, semantic search, and impact analysis to AI agents.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that indexes codebases into a queryable knowledge graph, enabling agents to answer structural questions like callers, callees, dependencies, and impact analysis through tools like callers, callees, deps, search, and impact.
      47 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that generates ranked, token-budgeted code structure maps using Tree-sitter AST analysis and PageRank, enabling AI agents to quickly understand unfamiliar codebases.
      2
      20 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that indexes codebases into a local knowledge graph, providing 52 AI tools for semantic search, call-graph traversal, git archaeology, and impact analysis to give AI agents deep understanding of code.
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents structured code understanding and precise code intelligence via local indexing of AST, call graphs, and semantic search.
      147 npm
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      RepoNova is an MCP server that builds a persistent knowledge graph of your codebase, enabling AI agents to query code structure, dependencies, and semantics through 11 specialized tools.
      174 npm
      7
      MIT

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tool purposes are largely distinct and descriptions explicitly route agents to the right one, but find_symbol/get_symbol and who_calls/blast_radius have adjacent responsibilities that could occasionally cause misselection. Overall, the overlap is minor and well-documented.

    Naming Consistency3/5

    All names are readable snake_case, but the set mixes verb-object names (find_symbol, search_code, get_symbol), question-style names (who_calls, what_it_calls), and noun-phrase names (blast_radius, file_summary, architecture_overview). This is not chaotic, but it lacks a single consistent naming pattern.

    Tool Count5/5

    Ten tools is a well-scoped surface for a code-graph analysis server. Each tool addresses a distinct job—search, symbol detail, call trees, impact analysis, overview, index health—without redundancy or bloat.

    Completeness4/5

    The toolchain covers symbol discovery, detailed lookup, dependency analysis, impact assessment, file outlining, architecture orientation, and index health, giving strong coverage of the code-understanding workflow. Minor gaps like direct raw-file access or listing all symbols in a file must be worked around via file_summary and get_symbol.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues