Skip to main content
Glama

Related Servers

Alternatives to memorepo

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Semantic code index and gatekeeper that exposes 14 read-only MCP tools for AI agents, enabling symbol search, definition lookup, reference finding, and impact analysis via static analysis of codebases.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides code intelligence for AI coding agents by indexing repositories into a hybrid knowledge graph, enabling agents to query dependencies, impact, and context through 28 MCP tools.
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables local code intelligence for AI agents and editors by indexing source code, dependencies, Git history, tests, and documentation, and provides change-impact analysis and relevant test selection through MCP.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a local, multi-repo code graph for symbol exploration, blast radius analysis, co-change mining, and durable code-anchored memory via MCP tools.
      288 npm
      14
      Business Source 1.1
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to query a compiled typed symbol graph over MCP, revealing real callers, callees, blast radius, data flow, constraints, dead code, and commit-history signals before editing. Supports repo syncing and ranked context retrieval so agents can avoid structural regressions.
      27
      67 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly separated roles: snapshot filesystem access (list_snapshot_files, read_snapshot_file, search_snapshot_text) versus CBM code-graph access (search_graph, trace_path, get_code_snippet, query_graph). The fuzziest boundaries are search_snapshot_text vs search_code (literal text across all files vs indexed code text) and list_space_repositories vs list_projects, but the descriptions explicitly draw these distinctions. An agent can pick correctly with careful reading, though the two search tools could still be misselected.

    Naming Consistency4/5

    Nearly all tools follow a verb_noun convention (list_snapshot_files, read_snapshot_file, search_snapshot_text, get_architecture, trace_path, search_code), with snapshot tools consistently prefixed by 'snapshot'/'space'. The exceptions are snapshot_index_coverage and index_status, which are noun phrases rather than verb-led, plus a mild inconsistency between 'get_' and 'search_'/'query_' retrieval verbs.

    Tool Count5/5

    Fourteen tools is well within a reasonable range and splits cleanly into two coherent surface layers (five snapshot-integrity tools, nine code-graph tools). Each tool corresponds to a distinct operation with no filler or duplicated capability, so the count is well matched to the server's dual purpose.

    Completeness4/5

    The read-only surface covers inventory, coverage reporting, file reading, literal search, project listing, indexing status, architecture, schema, graph search, path tracing, snippet lookup, and a Cypher escape hatch — a solid lifecycle for inspecting a code snapshot. Minor gaps remain: there is no way to enumerate snapshots/versions or diff two snapshots, and symbol-reference discovery depends on trace_path rather than a dedicated callers/callees tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues