Skip to main content
Glama
promplate

gh-mcp

by promplate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to gh-mcp

No user-submitted related servers found.

    Related Servers

    • github-mcp

      awernick
      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
      -

    • repogate

      JohnXu22786
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that wraps the GitHub REST API into tools for repo queries, issue/PR management, code review, search, and authentication, letting coding agents operate GitHub directly in conversations.
      1 npm
      MIT

    • github-mcp

      AbdeeBuilds
      A
      license
      A
      quality
      D
      maintenance
      GitHub MCP server for Claude Code, Cursor, Cline, Windsurf, and any MCP-compatible client. Exposes GitHub tools (issues, pull requests, code search, file content) to your LLM via the Model Context Protocol.
      7
      MIT

    • epik-gh

      epik-agent
      F
      license
      Not graded
      quality
      A
      maintenance
      A GitHub MCP server that wraps the gh CLI to expose GitHub operations like issues, pull requests, branches, labels, repositories, CI actions, and Projects V2 as tools for MCP clients.
      -

    • GitHub MCP Toolkit

      kartik-012
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: github_code_search is for exact substring searching of code files, while github_graphql is a general-purpose interface for all other GitHub queries and mutations. There is no functional overlap that would cause an agent to select the wrong tool.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern of 'github_<descriptive_noun>', using snake_case. The naming is predictable and clearly indicates the tool's domain and action.

    Tool Count3/5

    With only two tools, the server is minimal. The GraphQL tool is extremely powerful and can handle many operations, but it lacks dedicated tools for common GitHub tasks, making the surface feel incomplete for typical use cases.

    Completeness2/5

    The tool set lacks dedicated tools for fundamental GitHub operations such as listing repositories, creating issues, or managing pull requests. While the GraphQL tool can theoretically perform these, the absence of pre-built abstractions creates a significant gap in usability and increases complexity for agents.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources