Skip to main content
Glama
Eyalm321

github-mcp

by Eyalm321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to github-mcp

No user-submitted related servers found.

    Related Servers

    • GitHub MCP Server

      grysonbaltazar
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with the GitHub API, enabling AI assistants to query repositories, pull requests, issues, commits, users, and more.
      245 npm
      ISC

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

    • GitHub MCP Server

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

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

    C2.3/5.0

    Scored across 1043 tools

    Disambiguation4/5

    The consistent domain-prefixed naming makes most tools distinguishable, and each maps to a specific API endpoint. However, the sheer number of near-identical variants (org vs repo vs authenticated-user, legacy vs non-legacy, get vs list) creates some risk of misselection.

    Naming Consistency4/5

    Tool names overwhelmingly follow a snake_case domain_action_resource pattern, which is impressive across 1043 tools. Minor inconsistencies exist, such as mixing delete/remove and create/add, plus a few awkward compound names like custom_properties_for_repos_get...

    Tool Count1/5

    1043 tools is an extreme count for any agent-facing surface, far beyond the manageable range. Even if each tool is individually valid, the sheer volume makes efficient tool selection impractical and will overwhelm context windows.

    Completeness2/5

    The surface is extremely broad, covering many GitHub API domains, but notable gaps exist: there are no search tools and no release lifecycle tools (list/create/update/delete releases). These are significant missing capabilities for a GitHub-focused server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources