Skip to main content
Glama
MSPbotsAI

github-org-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to github-org-mcp

No user-submitted related servers found.

    Related Servers

    • github-mcp

      awernick
      F
      license
      A
      quality
      D
      maintenance
      MCP server exposing GitHub tools for issues, pull requests, and code browsing via the GitHub REST API. Designed for local LLM clients with flat arguments and streamable HTTP support.
      15
      -

    • GitHub MCP Server

      rriesco
      A
      license
      A
      quality
      C
      maintenance
      Python MCP server for GitHub operations, providing native tool integration with Claude Code and other MCP clients. It enables managing issues, pull requests, CI status, milestones, and batch operations via natural language.
      15
      MIT

    • 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.
      6 npm
      MIT

    • GitHub MCP Server

      piyushgithub15
      A
      license
      Not graded
      quality
      C
      maintenance
      Stateless Streamable HTTP MCP server exposing 5 GitHub tools (user info, repository metadata, file contents, issue listing, and issue creation) with token-based authentication required only for tool calls.
      48 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

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action and entity: members vs invitations, and within those, list/get/set/remove vs list/create/cancel. Two tools handle adding users (set_org_membership by username, create_org_invitation by ID/email), but their descriptions clearly differentiate the input method and state.

    Naming Consistency5/5

    All tool names follow the consistent pattern github_<verb>_org_<noun> using snake_case. Verbs are varied (list, get, set, remove, create, cancel) but the noun targets (members, membership, invitation) are clear and consistent.

    Tool Count5/5

    Seven tools are well-scoped for the purpose of managing GitHub organization membership. They cover both the member lifecycle and invitation lifecycle without unnecessary sprawl, fitting comfortably in the ideal 3-15 range.

    Completeness5/5

    The surface covers listing members, reading a specific membership, adding/updating, removing, plus listing invitations, creating invitations, and canceling invitations. This provides full CRUD-like coverage for the domain with no obvious dead ends or missing essential operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources