Skip to main content
Glama

Related Servers

Alternatives to LayerMap

No user-submitted related servers found.

    Related Servers

    • 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.
      Functional Source , Version 1.1, ALv2 Future
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and terminal users to query codebases for callers, impact, tests, dependencies, and refactor previews using static AST analysis, with every match accounted for and uncertain relationships clearly marked.
      226 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM agents to efficiently understand and navigate a codebase by providing semantic search over symbols and a reference graph, replacing expensive grep/glob calls with structured tools like definition lookup, caller/callee queries, and change-impact analysis.
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides local-first repository architecture analysis with file-level proof, enabling agents to map codebases, locate implementations, trace call paths, and assess change impact with deterministic evidence.
      4 npm
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents and developers to search code by meaning and exact text, map symbols, dependencies, blast radius and context, inspect git-change impacts, and trace live Python or JavaScript execution from a local air-gapped SQLite index.
      Apache 2.0

    TDQS

    A4.5/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools have mostly distinct roles: search declarations, explore the call map, list exact references, and run a change-impact report. The main overlap is between project_explore_map's cached caller view and project_find_references' broader usage listing, though the descriptions explicitly contrast them.

    Naming Consistency5/5

    All tools use a consistent snake_case project_verb_noun pattern: project_search_map, project_explore_map, project_find_references, project_check_changes. The convention is predictable and readable throughout.

    Tool Count5/5

    Four tools is well scoped for a static code-map server. Each tool covers a distinct step in the workflow: discovering declarations, exploring relationships, enumerating references, and checking change impact.

    Completeness4/5

    The surface covers search, declaration/file exploration, caller/callee tracing, reference lookup, and change-impact analysis, which is core coverage for the domain. Minor gaps remain: there is no dedicated source-reading tool and explicitly no full-text search, though the descriptions tell the agent to read source at reported line ranges.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues