Skip to main content
Glama
fvanevski

gh_mcp

by fvanevski
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 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.
      8 npm
      1
      ISC

    • mcp-github

      Livshitz
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the GitHub REST API that enables interaction with repositories, pull requests, issues, branches, commits, reviews, and code search, with configurable write and destructive operations.
      -

    • github-mcp

      anujsingla
      F
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that exposes GitHub user profiles, repository info, and search via tools for AI assistants like Claude.
      -
    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

    B3.2/5.0

    Scored across 61 tools

    Disambiguation2/5

    While descriptions are unusually detailed, several tool boundaries are genuinely unclear: gh_get_issue explicitly covers pull requests alongside gh_get_pr, gh_get_run_logs/gh_get_job_logs/gh_get_failed_run_logs all overlap on log retrieval, and gh_get_pr_review_state/gh_get_pr_review_eligibility/gh_get_merge_requirements serve similar review-status purposes. An agent selecting among these related tools faces real misselection risk.

    Naming Consistency4/5

    The vast majority follow a consistent gh_verb_noun snake_case pattern: gh_list_*, gh_get_*, gh_create_*, gh_edit_*, gh_set_*. Minor deviations like gh_commit_files, gh_watch_run, and the 'exact' suffix on gh_create_release_exact/gh_run_workflow_exact are understandable but slightly break the otherwise predictable scheme.

    Tool Count1/5

    61 tools is far beyond the well-scoped range and falls into the extreme mismatch category. Even given GitHub's breadth, many micro-specialized read-only variants (multiple log, artifact, and review-state tools) could be consolidated to reduce selection burden.

    Completeness2/5

    Despite the large read surface, there are significant lifecycle gaps: pull requests cannot be closed, branches cannot be listed or deleted, workflow runs cannot be cancelled, and labels/releases/milestones lack full update/delete coverage. These missing operations will cause agent dead ends in common GitHub workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources