Skip to main content
Glama

Related Servers

Alternatives to ContextPro

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to explore TypeScript, JavaScript, and Prisma projects through local symbol, call, and model-usage graphs, while recalling persistent project-scoped decisions and returning focused source context.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to retrieve focused code context—signatures, complete symbol bodies, related types and imports, line excerpts, and AST-labeled Git diffs—across TypeScript, JavaScript, Python, and Go, with batched requests and token-efficient pagination.
      1
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to query a static AST-based call graph for TypeScript/JavaScript repositories, including who-calls, impact analysis, entry-to-dependency traces, hotspots, symbol search, and git-blame archaeology, with every result backed by source evidence chains.
      9
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to interrogate a local repository deterministically for symbols, dependencies, call paths, routes, tests, and Git impact, returning verified structured evidence with exact line citations instead of requiring the whole codebase to be read.
      79 PyPI
      4
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to retrieve bounded, focused context from a local structural code graph, including source entities, Git relationships, and recorded project memory. It supports exploring structure, inspecting callers, callees, and impact, and carrying prior mistakes into later sessions without reading full files.
      24 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: grep vs search vs blast_radius vs exact_references are explicitly differentiated by literal/semantic/binding behavior, and status/reindex/task_pack cover separate lifecycle stages. There is still some conceptual overlap among skeleton, explain, artifact_read, and task_pack as ways to retrieve context, but the descriptions give enough guidance to select between them.

    Naming Consistency3/5

    All names use snake_case casing, but the semantic pattern is mixed: some are verbs (search, grep, reindex, explain), some are nouns (skeleton, status, task_pack), and others are noun_verb or verb_noun compounds (artifact_read, memory_record_task). The names remain readable, but there is no single predictable verb_noun convention throughout.

    Tool Count5/5

    At 14 tools, the set is well within a reasonable range for a code-context and analysis server. Each tool appears to serve a distinct workflow: indexing, search, symbol analysis, task packaging, memory, validation, and reporting.

    Completeness4/5

    The surface covers index lifecycle, semantic and literal search, reference analysis, symbol extraction, task context assembly, and memory persistence, which is broad for the domain. There are minor gaps: no explicit artifact write/list operation, no direct source-reading/context tool despite being referenced in descriptions, and no separate memory recall/list tool beyond task_pack.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues