Skip to main content
Glama
pblarismendi

mcp-github-server

by pblarismendi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-github-server

No user-submitted related servers found.

    Related Servers

    • okffs

      neturely
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets Claude Code manage GitHub issues, branches, and pull requests through natural language, automating the full development workflow from planning to closing.
      523 npm
      2
      MIT

    • GitHub MCP Server

      Xiao-rx
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to directly manage GitHub repositories, including PRs, issues, and code search, using natural language.
      MIT

    • GitHub MCP Server

      ualUsham
      F
      license
      B
      quality
      D
      maintenance
      An MCP server that enables Claude and other compatible LLMs to interact with the GitHub API, supporting features like creating issues, retrieving repository information, listing issues, and searching repositories.
      4
      -

    • devscope-mcp

      peteroyce
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that gives Claude live access to your GitHub workspace — PR reviews, issue triaging, repo search, and weekly digest reports through natural language.
      7
      MIT

    • GitHub MCP Server

      MuyleangIng
      F
      license
      Not graded
      quality
      D
      maintenance
      A working MCP server that connects to the real GitHub API, enabling users to manage repositories, issues, pull requests, and more through natural language in Claude Desktop.
      -
    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 39 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between search, get, list, create, update, delete, and close operations. Even similar operations like close_issue and update_issue are distinct in purpose and description.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, with verbs like list, get, create, update, delete, close, merge, and search. The naming clearly communicates the action and target resource without mixing conventions.

    Tool Count2/5

    With 39 tools, the server is significantly larger than typical MCP servers. While many GitHub operations are covered, the count exceeds the practical threshold for agent navigation, making it feel bloated and hard to manage.

    Completeness3/5

    The tool set covers many GitHub features—repos, issues, PRs, webhooks, releases, tags—but lacks repository creation, file operations, and delete/update for several resources such as issues, releases, and tags, creating dead ends in common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources