Skip to main content
Glama

Related Servers

Alternatives to droidmap

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Local code graph for coding agents: the files a change will break (blast radius), where a symbol is used, and the architecture of each part of a repository. Deterministic static parsing with tree-sitter, no model and no network.
      18
      14
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a dependency graph of any local repository with tools for change impact, transitive dependents, health audits, and more, enabling AI coding agents to see structure and refactor safely.
      4,912 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to query a deterministic AST knowledge graph of a codebase over MCP—finding symbols, callers/callees, dependencies, impact, and relevant tests via compact path:line JSON—so they can navigate code without grepping, embeddings, or an LLM.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and reviewers to query a deterministic code dependency graph for callers, routes, pages, tables, and config with file:line evidence instead of grepping. One server can serve many indexed graphs, supporting cross-repository impact analysis.
      329 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a precise, local call/type/data graph so they can find who calls what, what breaks when code changes, and which tests to run, with every answer traced to file:line.
      99 PyPI
      1
      Functional Source , Version 1.1, ALv2 Future

    TDQS

    A4.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action on the code graph: check (rule linting), diff (git change mapping), impact (transitive dependents), show (single-node detail), find (node search), report (project overview), explain (rule documentation). Descriptions even include explicit sibling disambiguation cues like 'use droidmap_diff for what a change touches' and 'use droidmap_impact for transitive, droidmap_show for direct links'.

    Naming Consistency5/5

    Every tool is a single lowercase word appended to a uniform 'droidmap_' namespace prefix, forming a predictable droidmap_<action> pattern. No camelCase mixing or inconsistent verb styles; the naming reads like a coherent family of graph/analysis operations.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and each earns its place with a non-redundant role in a codebase-graph analysis workflow. Nothing feels padded or missing from the set.

    Completeness4/5

    The surface covers the full exploratory lifecycle: find a node, inspect it, map its dependents, diff changes, lint rules, understand findings, and get a whole-project report. The main minor gap is baseline handling: findings are excluded via droidmap-baseline.json, but no tool exists to create or update that baseline, leaving agents to work around it externally.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues