Skip to main content
Glama

Related Servers

Alternatives to Solumbe

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Local-first codebase context engine that parses code into a ranked dependency graph and serves it to AI tools via MCP for deep structural understanding.
      5
      19 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Local-first code intelligence MCP server with hybrid BM25 + ONNX vector search, symbol-level impact analysis, diff-aware PR review with risk scoring, and persistent memory tied to git state.
      36
      132 npm
      80
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Local-first MCP server that turns project documentation and source code into durable, evidence-backed context for AI agents, with bounded retrieval and explicit gap reporting.
      8
      1,003 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server that indexes all projects on your machine and provides coding agents with briefings about each project's stack, services, and run instructions, so they can start sessions with context across all repos. No cloud, no accounts, no telemetry.
      25 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Turn your codebase into AI context — entirely on your machine. Single-binary MCP server with AST parsing, call graph, and local embeddings.
      26
      MIT

    TDQS

    A3.9/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools carve out distinct roles, and descriptions explicitly cross-reference siblings (review_context vs review_verdict vs review_gate; repo_index vs repo_map vs repo_search). Some inherent overlap remains among the analysis engines (change_impact, context_pack, agent_experience, convergence_score), which all consume a task/repo and could be confused by a new agent despite the guidance.

    Naming Consistency4/5

    All names are snake_case and grouped under clear prefixes (repo_*, review_*), which aids navigation. However the verb/noun form is mixed, with verb-style names (repo_inspect, repo_search, change_impact, model_route) alongside noun-style names (agent_experience, context_pack, convergence_score, workspace_report).

    Tool Count4/5

    14 tools is within a healthy range for a repo-intelligence suite and each covers a defensible capability. There is mild redundancy since composite tools (review_verdict) are composed from others (change_impact, review_context, review_gate), so a few could be consolidated.

    Completeness4/5

    The surface covers indexing, search, mapping, impact analysis, review/gating, convergence scoring, context packing, model routing, and workspace reporting — a broad lifecycle for repo understanding. Gaps are minor: it is entirely read-only/advisory with no apply/edit or catalog-mutation management beyond repo_index.

    Maintenance

    ActivityActive
    ResponsivenessResponsive