Skip to main content
Glama

Related Servers

Alternatives to Git RAG MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A production-grade MCP server that provides LLMs with safe, structured, tool-based access to GitHub repositories, including issue management, semantic search, and guarded write operations.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that gives AI agents access to developer tooling — GitHub (read-only), documentation search, and web research — via stdio transport.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to retrieve cited git-history explanations for files and tickets, compile a Team Engineering Contract from repository artifacts, and follow guided Understand/Build workflows over MCP stdio. It lets clients such as Grok, Claude Code, Codex, Kiro, and Cursor share the same tools for evidence-backed repository understanding.
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM hosts to perform scoped GitHub operations over stdio, including repository intelligence, pull request lifecycle and diff inspection, and commit history queries. It exposes 12 FastMCP tools backed by PyGithub for repository, PR, and commit workflows.
      -
    • F
      license
      A
      quality
      D
      maintenance
      MCP server exposing GitHub tools for issues, pull requests, and code browsing via the GitHub REST API. Designed for local LLM clients with flat arguments and streamable HTTP support.
      15
      -

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    Create_test_case is distinct in purpose from the two validate_* tools. The two validators are parallel and could be momentarily confused, but their names clearly indicate the GitHub vs RAG domain, so boundaries are mostly clear.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: create_test_case, validate_github_result, validate_rag_result. The convention is predictable and uniform.

    Tool Count4/5

    Three tools is a small but reasonable set for a focused testing utility. It is slightly on the low side, but each tool has a clear role and the count does not feel excessive or arbitrarily inflated.

    Completeness2/5

    The domain is a testing harness for MCP tools, yet there is no tool to run a test case, list/retrieve existing test cases, or update/delete them. Validation covers only GitHub and RAG results, leaving other potential MCP results unsupported, which creates significant gaps for realistic workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues