Skip to main content
Glama
MSPbotsAI

github-org-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
github_list_org_membersA

List members of the GitHub organization.

    Args:
        role: Filter by member role — "all", "admin", or "member" (default: "all").
        filter: Filter members — "all" or "2fa_disabled" (default: "all").
        per_page: Results per page, max 100 (default: 30).
        page: Page number of the results to fetch (default: 1).
github_get_org_membershipA

Get a user's membership (role and state) in the organization.

    Args:
        username: The GitHub handle of the user to look up.
github_set_org_membershipA

Add a user to the organization or update their role.

    If the user is not yet a member, GitHub sends an invitation (state "pending");
    if they already are a member, their role is updated.

    Args:
        username: The GitHub handle of the user to add or update.
        role: Role to assign — "member" or "admin" (default: "member").
github_remove_org_memberA

Remove a user from the organization.

    Removing a member also removes them from all teams and revokes their
    access to organization repositories.

    Args:
        username: The GitHub handle of the user to remove.
github_list_org_invitationsA

List the organization's pending member invitations.

    Args:
        per_page: Results per page, max 100 (default: 30).
        page: Page number of the results to fetch (default: 1).
github_create_org_invitationA

Invite a user to the organization by GitHub user ID or by email.

    Exactly one of invitee_id or email must be provided.

    Args:
        invitee_id: GitHub numeric user ID of the person to invite.
        email: Email address of the person to invite (for users without a known ID).
        role: Invitee role — "direct_member", "admin", or "billing_manager"
            (default: "direct_member").
        team_ids: Optional list of team IDs to add the invitee to.
github_cancel_org_invitationA

Cancel a pending organization invitation.

    Args:
        invitation_id: The numeric ID of the invitation to cancel
            (from github_list_org_invitations).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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