Skip to main content
Glama
awernick

github-mcp

by awernick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to github-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      C
      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

    • @cloud9-labs/mcp-github

      cloud9-labs
      A
      license
      B
      quality
      D
      maintenance
      MCP (Model Context Protocol) server for GitHub API integration. This server provides comprehensive tools for interacting with GitHub repositories, issues, pull requests, branches, and code search through a unified interface.
      15
      2 npm
      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.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: issues, PRs, repos, code, file contents, and user info. Search tools are clearly separated by domain (issues, repos, code), and comment tools are distinct for issues vs PRs. No meaningful overlap.

    Naming Consistency5/5

    All names follow a consistent verb_noun snake_case pattern (get_, list_, create_, update_, add_, search_). Even edge cases like 'get_me' and 'get_file_contents' fit the pattern, with no mixing of camelCase or other styles.

    Tool Count5/5

    15 tools is at the upper boundary of the ideal range but each one earns its place. The set covers core GitHub workflows without unnecessary redundancy, and the count is well-proportioned to the server's scope.

    Completeness4/5

    Issue management is complete (list, get, create, update, comment, search). PR management covers list, get, create, and comment, but lacks update and merge operations, which are common lifecycle actions. Repo exploration is solid with get/search, and code/file retrieval is covered. Minor gaps exist, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources