Skip to main content
Glama
PhialsBasement

GitHub MCP Server Plus

by PhialsBasement
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to GitHub MCP Server Plus

No user-submitted related servers found.

    Related Servers

    • @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
      12 npm
      MIT

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

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

    • git-mcp

      abhi-d-git
      F
      license
      Not graded
      quality
      D
      maintenance
      Standalone MCP server for GitHub that enables repository management, branch operations, pull request handling, and commit retrieval via tools listed in the README.
      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

    B3.3/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific GitHub resources and actions, but there is some overlap between push_files_content and push_files_from_path (both push multiple files, differing only in input source) and between list_issues and search_issues (both retrieve issues, differing in scope). Descriptions help clarify these distinctions, but agents might occasionally confuse them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun or verb_noun_preposition pattern (e.g., create_issue, get_file_contents, search_repositories), with no mixing of conventions like camelCase or snake_case variations. The naming is predictable and readable throughout the set.

    Tool Count4/5

    With 18 tools, the count is slightly high but reasonable for a comprehensive GitHub server covering repositories, issues, files, search, and operations. It avoids being excessive (under 25) and each tool appears to serve a specific function, though some could be consolidated (e.g., the two push tools).

    Completeness5/5

    The tool set provides complete coverage for core GitHub workflows, including CRUD operations for repositories, issues, files, and branches, along with search across code, issues, repositories, and users. There are no obvious gaps; agents can perform end-to-end tasks like creating repos, managing issues, and pushing code without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources