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
      10 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      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
      314 npm
      82
      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
      256 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      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.
      6 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation3/5

    The descriptions do heavy lifting with explicit cross-references (review_verdict = change_impact + review_context + review_gate; use review_context for diff only, etc.), but real overlaps remain: change_impact and context_pack both rank files for a task, repo_map and repo_search both narrow by domain/kind/route, and repo_inspect versus repo_map both profile repository shape. An agent can usually sort it out from the text, but several boundaries require reading before choosing.

    Naming Consistency4/5

    Everything is snake_case and grouped with sensible prefixes (repo_*, review_*), which keeps it predictable. However the internal pattern mixes verb_noun (repo_inspect, review_gate) with noun_noun (convergence_score, agent_experience, workspace_report) and a noun_verb outlier (context_pack), so naming is not a clean single convention.

    Tool Count4/5

    14 tools sits comfortably in the well-scoped range and each tool maps to a recognizable step in the repo-analysis/review lifecycle. It is arguably one or two tools heavier than needed given the composite tools already bundle sub-capabilities, but nothing feels gratuitous.

    Completeness4/5

    The surface covers the full arc: index, inspect, map, search, context packing, impact, gating, verdict, convergence scoring, model routing, and multi-repo reporting, plus a harness generator. Missing pieces are minor for an analysis-focused server (no direct file-read or doc/comment-fetch tool), and these are workarounds rather than blockers.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues