github-org-mcp
This server exposes GitHub organization member-management operations (via the GitHub REST API) as MCP tools, usable by Claude or any MCP client, with per-request OAuth token and org supplied via HTTP headers.
List organization members — filter by role (
all/admin/member) and 2FA status, with pagination.Get a user's membership — look up a member's role and membership state by username.
Add a user or change their role — invite non-members (state
pending) or update an existing member tomember/admin.Remove an organization member — revoke access, also removing them from all teams and org repositories.
List pending invitations — view outstanding org invitations with pagination.
Create an invitation — invite by GitHub user ID or email, assign role (
direct_member/admin/billing_manager), and optionally add to teams.Cancel an invitation — revoke a pending invitation by its numeric ID.
All operations act on the org resolved from the request context (X-GitHub-Org) using the caller's token (X-GitHub-Token), so write actions require an org owner or an app with org-members permission.
Provides tools for managing GitHub organization membership: listing organization members and pending invitations, viewing and updating membership roles, adding or removing members, and creating or canceling invitations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@github-org-mcp list all members in the organization"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
github-org-mcp
A stateless HTTP MCP service that exposes GitHub organization member management (list / view / add / update role / remove members, and manage invitations) as Model Context Protocol (MCP) tools consumable by Claude and other MCP clients.
The OAuth flow is handled upstream — this service does not perform OAuth. The caller passes a GitHub OAuth access token and the org slug on each request via HTTP headers; the service maps the token to Authorization: Bearer <token> when calling the GitHub REST API.
MSPbots Connector
The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.
Get started at connect.mspbots.ai →
MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.
Hosted service: connect.mspbots.ai · Free to use.
Why Connector

Visible | Every tool call is logged: who, which vendor, when. Usage dashboard, CSV export, SIEM streaming. |
Controlled | Role-based, per-tool allowlist. Deny by default. |
Protected | Credentials encrypted per record. AI clients never see your vendor passwords or tokens. |
MSP-native | Built for the MSP stack only: RMM, PSA, documentation, security, finance. |
Quick start
Sign up at connect.mspbots.ai.
Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.
Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.
Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.
Ask your AI to do real work, and watch every call appear in the audit log.
Features
Unified gateway
One MCP URL for all your AI clients
150+ connectors across the MSP stack
Custom MCP servers supported, free
Authorization happens on each vendor's own page; the AI never sees passwords or tokens
Bring your own credentials: use the vendor API keys you already have
Multiple accounts per app; connect once, reuse across AI clients
Tool search: finds the right action for the task
One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically
Visibility
Audit log for every tool call (who, which vendor, when)
Usage dashboard: call volume, top vendors, error rate, per-user activity
Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)
Optional recording of tool arguments and result summaries (off by default, enabled per organization)
Control
Per-role, per-tool allowlist, deny by default
owner / admin / member roles
SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace
Security
Credentials encrypted one record at a time (AES-256-GCM, per-record key)
AI clients authenticate with OAuth 2.1 + PKCE
Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.
Static egress IP for customer firewall and API allowlisting
Pricing
Free.
Links: connect.mspbots.ai · mspbots.ai
Related MCP server: github-ops-mcp
Architecture
Stateless — no user state, no credential storage, no session data persisted between requests.
Concurrent-safe — per-request credential isolation via Python
contextvars; concurrent requests never bleed token/org.Dual auth modes — per-request credentials via HTTP headers (
gatewaymode, default, SOP-compliant) or single shared credentials (envmode, local dev only).Two transports — HTTP server (
MCP_TRANSPORT=http) for production, stdio (MCP_TRANSPORT=stdio) for local development.
Endpoints
Method | Path | Description |
POST |
| MCP protocol entry point |
GET |
| Health check |
Default port: 8080 (configurable via MCP_HTTP_PORT).
Authentication — HEADER Parameters
In gateway mode (default), every POST /mcp request must carry both headers below. Requests missing either header receive 401. Credentials are never stored globally or persisted; each request's token and org live only in a contextvars.ContextVar and are reset when the request completes.
Client → this service | this service → GitHub upstream |
|
|
| URL path segment |
Header | Type | Required | Default | Allowed values | Description | Example |
| string | Yes | None | None | GitHub OAuth access token; mapped to |
|
| string | Yes | None | None | GitHub organization login/slug the tools operate on. |
|
The header names are configurable via
GITHUB_TOKEN_HEADER/GITHUB_ORG_HEADER.
Service Parameters
Variable | Required | Default | Description |
| No |
|
|
| No |
| HTTP header carrying the OAuth token in |
| No |
| HTTP header carrying the org slug in |
| env mode only | — | OAuth access token used in |
| env mode only | — | Org slug used in |
| No |
| GitHub REST API base URL (change for GitHub Enterprise Server) |
| No |
| Transport: |
| No |
| HTTP listen port |
| No |
| HTTP listen host |
Auth Modes
gateway mode (default, production, SOP-compliant):
Each request must include the
X-GitHub-TokenandX-GitHub-Orgheaders.No credentials are stored globally — isolated per request via Python
contextvars.Returns
401if either header is missing.
envmode (local dev only — not SOP-compliant for production):
Set
AUTH_MODE=env,GITHUB_TOKEN, andGITHUB_ORGin the environment or.env.All requests share the same credentials loaded at startup — violates per-request credential isolation.
Do not use in production or multi-tenant deployments.
Tool List
All tools follow the naming convention github_<action>_<resource> and operate on the org resolved from the request context (X-GitHub-Org).
Tool | Description | Parameters |
| List members of the organization |
|
| Get a user's membership role and state |
|
| Add a user to the org or update their role (invites if not a member) |
|
| Remove a user from the org (also removes from all teams) |
|
| List pending member invitations |
|
| Invite a user by user ID or email |
|
| Cancel a pending invitation |
|
The token's OAuth scopes / org permissions determine which operations succeed. Write operations (
set/remove/create/cancel) require the token to belong to an org owner or an app with the appropriate org-members permission.
Quick Start
Local development (stdio)
cp .env.example .env
# Edit .env: set GITHUB_TOKEN, GITHUB_ORG, AUTH_MODE=env, MCP_TRANSPORT=stdio
uv sync
python -m github_org_mcpHTTP server (gateway mode — default, SOP-compliant)
MCP_TRANSPORT=http python -m github_org_mcp
# Pass credentials per-request via X-GitHub-Token and X-GitHub-Org headersDocker
docker compose up --buildTest Examples
Health check
curl http://localhost:8080/healthExpected response:
{"status": "ok", "transport": "http", "auth_mode": "gateway"}Missing headers → 401 (gateway mode)
curl -i -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
# → HTTP/1.1 401, body includes "required_headers": ["X-GitHub-Token", "X-GitHub-Org"]List MCP tools
curl -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-GitHub-Token: your_oauth_access_token" \
-H "X-GitHub-Org: my-company" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'Call a tool — list org members
curl -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-GitHub-Token: your_oauth_access_token" \
-H "X-GitHub-Org: my-company" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "github_list_org_members",
"arguments": {"role": "all", "per_page": 30, "page": 1}
}
}'Call a tool — invite a user by email
curl -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-GitHub-Token: your_oauth_access_token" \
-H "X-GitHub-Org: my-company" \
-d '{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "github_create_org_invitation",
"arguments": {"email": "newhire@example.com", "role": "direct_member"}
}
}'Security
Credentials are never stored globally or persisted between requests.
Each request's token and org are isolated in
contextvars.ContextVarand reset after the request completes.The service runs as a non-root user (
github, uid 1001) inside the container.Never commit real tokens or org secrets —
.gitignoreexcludes.env.
Available Tools
7 toolsgithub_cancel_org_invitationA
Cancel a pending organization invitation.
Args:
invitation_id: The numeric ID of the invitation to cancel
(from github_list_org_invitations).
Inputs: invitation_id (required). Returns: result
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.
Inputs: role, email, team_ids, invitee_id. Returns: result
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.
Inputs: username (required). Returns: result
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).
Inputs: page, per_page. Returns: result
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).
Inputs: page, role, filter, per_page. Returns: result
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.
Inputs: username (required). Returns: result
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").
Inputs: username (required), role. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
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.
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.
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.
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
Related MCP Connectors
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Create, deploy, and operate MCP servers directly from your GitHub repositories.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Related MCP Servers
- AlicenseAqualityDmaintenancePython 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.15MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides operational tooling over the GitHub API — issue triage, PR review monitoring, repo health audits, and team access reviews.111MIT
- FlicenseAqualityDmaintenanceMCP 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-
- AlicenseNot gradedqualityBmaintenanceMCP 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.5 npmMIT