Skip to main content
Glama
shade-solutions

github-mcp-plus

by shade-solutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to github-mcp-plus

No user-submitted related servers found.

    Related Servers

    • mcp-github

      nhevers
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and code search.
      -

    • 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 Prod MCP

      nouhailadahmany
      A
      license
      C
      quality
      D
      maintenance
      A production-ready MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and more via both MCP stdio and REST API.
      27
      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.
      8 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

    C2.7/5.0

    Scored across 73 tools

    Disambiguation3/5

    Many tools are distinct, but several have overlapping boundaries, e.g., issue_read vs get_pull_request, list_pr_files vs get_pr_diff, and add_issue_comment vs add_pr_review_comment. Descriptions help clarify some, but the large number of similar tools creates significant potential for misselection.

    Naming Consistency4/5

    The vast majority follow a consistent verb_noun pattern (get_, list_, create_, update_, delete_). However, a few deviations like actions_list and actions_run_trigger break the pattern, and get_pr_diff is inconsistent with the more common list_/get_ pairing.

    Tool Count2/5

    At 73 tools, this server far exceeds the typical well-scoped count. While it covers many GitHub API endpoints, the sheer number makes the toolset unwieldy and likely to overwhelm agents, especially with many niche features (enterprise, codespaces, SSH keys) that could be omitted or bundled.

    Completeness4/5

    The toolset covers repositories, branches, commits, issues, pull requests, releases, gists, users, organizations, webhooks, deployments, and more, providing extensive lifecycle coverage. Minor gaps exist (e.g., no delete branch, no list labels, no delete gist), but the overall surface is remarkably complete for GitHub operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources