Skip to main content
Glama
ibmkevin

github-mcp-server

by ibmkevin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to github-mcp-server

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

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

    • github-mcp-bridge

      SamNewhouse
      F
      license
      Not graded
      quality
      B
      maintenance
      A lightweight MCP server that exposes GitHub operations as tools over HTTP, enabling any MCP-compatible client to interact with GitHub repositories without a built-in connector.
      1
      -
    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.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly different resource and action: searching repositories, listing issues, and reading file contents. There is no meaningful overlap between them.

    Naming Consistency5/5

    All tool names follow the same lowercase snake_case verb_noun pattern: search_repositories, list_issues, read_file_contents. The convention is consistent and predictable.

    Tool Count3/5

    Three tools is on the low end for a server named github-mcp-server. While the set is focused and each tool earns its place, the name implies a broader GitHub surface than three read-only operations.

    Completeness2/5

    The server lacks many core GitHub operations such as getting a single repository, creating or updating issues, listing pull requests, or exploring file paths before reading them. Agents would frequently hit dead ends, especially after searching for a repo or listing issues.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources