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
      Not graded
      quality
      A
      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.
      1
      MIT
    • A
      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.
      258 PyPI
      4
      MIT
    • 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.
      35 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have distinct roles, and potentially overlapping pairs such as search/grep, exact_references/blast_radius, and skeleton/explain are explicitly differentiated in their descriptions. A few boundaries remain soft, especially between structural overview tools and usage-analysis tools, but an agent can generally choose correctly.

    Naming Consistency3/5

    All names use snake_case, which keeps them readable, but the naming patterns are mixed: some are single verbs (search, grep, explain), some are nouns (skeleton, status, task_pack), some are verb_noun (discover_tools, validate_scope), and one is noun_verb_noun (memory_record_task). The set is understandable but not predictably patterned.

    Tool Count5/5

    With 14 tools, the server is within a well-scoped range for a code-context and indexing assistant. Each tool appears to serve a specific workflow, and the count is neither thin nor excessive.

    Completeness3/5

    The core code-context workflows are covered: discovery, search, references, structural explanation, reindexing, status, task packing, and memory recording. However, validate_scope references an edit_scope step that is not present, and artifact/memory surfaces are incomplete because there is no obvious way to list artifacts or query memory records directly.

    Maintenance

    ActivityActive
    ResponsivenessNo issues