Skip to main content
Glama

Related Servers

Alternatives to repo-context

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Local, read-only MCP server for coding agents. Indexes repeated implementations in your repository (FastAPI routes, pytest fixtures, Pydantic and SQLAlchemy models) and returns source-backed examples with a bounded read plan, or a typed UNKNOWN when evidence is insufficient. No LLM or network calls.
      1
      3 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Local-first code context CLI + MCP server: discover, index, and search repos; generate task-aware context packs, code maps, agent harnesses, and PR-review/merge-readiness gates for coding agents and reviewers.
      14
      400 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides autonomous codebase exploration through a plan-execute-reflect-report pipeline, generating onboarding reports with file:line references. Exposes both a high-level investigation tool and low-level read-only file access tools via MCP.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables people and AI agents to query local code repositories as graphs through stdio MCP tools for project listing, search, dependency tracing, impact analysis, bridge detection, node inspection, bounded code reading, and optional LSP definition/reference lookups.
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to read and search code across many git repositories — files at any branch, tag or commit, history, diffs, blame and cross-repo search — over local paths or remote hosts like GitHub, GitLab and Bitbucket. It is read-only by construction, hiding secrets found in files and working with any MCP client over stdio or Streamable HTTP.
      1
      Apache 2.0

    TDQS

    D1.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of ambiguity between tools.

    Naming Consistency5/5

    With a single tool, naming consistency is inherently perfect; no pattern deviations exist.

    Tool Count2/5

    A single tool is far too few for a server presumably focused on repository context, suggesting an underdeveloped or trivial surface.

    Completeness1/5

    A single generic 'explore' tool without any specialized operations (e.g., get commits, list branches) is severely incomplete for repository exploration.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues