Skip to main content
Glama
yukkie

gh-mcp

by yukkie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to gh-mcp

No user-submitted related servers found.

    Related Servers

    • 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

      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
      -

    • gh_mcp

      fvanevski
      A
      license
      B
      quality
      A
      maintenance
      A Python MCP server that wraps the GitHub CLI (gh) to provide structured tools for searching, reading, and managing GitHub resources like repos, issues, PRs, releases, and workflows, with write commands disabled by default.
      61
      MIT

    • GitHub CLI MCP Server

      munch-group
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps the GitHub CLI to provide comprehensive access to repository management, pull requests, issues, and workflows. It enables users to perform complex GitHub operations and interact with the GitHub API through a standardized interface.
      6 npm
      1
      ISC
    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 4 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair: create issue, comment on issue/PR, edit issue body, create PR. No two tools overlap in purpose, making selection unambiguous.

    Naming Consistency5/5

    All tools follow the consistent `gh_<resource>_<action>` pattern (gh_issue_create, gh_issue_comment, gh_issue_edit, gh_pr_create), making the function of each tool predictable.

    Tool Count5/5

    The four tools form a focused, well-scoped set for GitHub issue and PR creation and editing. The count is within the ideal 3-15 range and each tool earns its place.

    Completeness2/5

    The set lacks read operations (list/get issues or PRs) and PR lifecycle management (merge, close). An agent cannot discover existing resources or manage them beyond creation and editing, leaving significant functional gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources