Skip to main content
Glama
MissionSquad

mcp-github

by MissionSquad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-github

No user-submitted related servers found.

    Related Servers

    • mcp-github

      Livshitz
      F
      license
      Not graded
      quality
      D
      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.
      -

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

    • gh-mcp

      promplate
      F
      license
      A
      quality
      B
      maintenance
      Refined MCP server for GitHub GraphQL API. GitHub's official MCP Server exposes dozens of low-level tools that bloat token usage and are mostly impractical for LLMs. gh-mcp achieves the best of both worlds by providing a single, powerful interface: GitHub GraphQL, wrapped with smart abstractions.
      2
      -
    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 45 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific GitHub resources and actions, but there is some overlap between search_issues and list_issues (both handle issues), and get_combined_status vs get_commit_statuses (both related to commit statuses). Descriptions help differentiate, but agents might occasionally misselect between these pairs.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout (e.g., create_issue, list_commits, search_code), with no mixing of conventions like camelCase or snake_case. This predictability makes it easy for agents to understand and use the toolset.

    Tool Count2/5

    With 45 tools, this server feels overly heavy for a GitHub integration, as many tools could be consolidated or omitted without losing functionality. A typical well-scoped server has 3-15 tools; this exceeds that range significantly, potentially overwhelming agents and increasing complexity.

    Completeness5/5

    The toolset provides comprehensive coverage of GitHub's domain, including CRUD operations for issues, pull requests, repositories, projects, releases, and packages, along with search, status, and file management. No obvious gaps exist; agents can handle full workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources