GitHub MCP server: scoped access for every coding agent

Server release v1.12.2. Toolsets switch in AIPx without reconnecting.

Why use GitHub MCP when Claude Code already has git

Local git sees what’s on disk. GitHub MCP reaches what never lands there: issue threads, PR reviews, the logs of a red Actions run. get_job_logs returns every failed job in one call, so “why did main break” stops being a copy-paste session. Add Sentry MCP and PostHog MCP and the agent goes from production error to PR to release effect.

Claude’s built-in GitHub integration only syncs branch files, and ChatGPT’s connector only reads (ChatGPT MCP server). Claude Code GitHub Actions isn’t MCP at all. More in all AIPx integrations.

Official GitHub MCP server: remote, local and the registry

github/github-mcp-server is MIT-licensed and runs as a remote MCP server at https://api.githubcopilot.com/mcp/ or locally in Docker, per the official GitHub MCP server documentation. Every agent signed in as you shares one 5,000 requests per hour REST limit. The GitHub MCP Registry, launched September 16, 2025, is a catalog of servers like our MCP server list, not a server.

Connect GitHub MCP to Claude, Claude Code, Cursor or Codex

GitHub’s guides wire Claude Code, Cursor and Codex with a personal access token: one PAT per client config, each expiring on its own schedule. For Claude Desktop the Claude install guide says the OAuth route “is not currently supported.” AIPx is an MCP gateway with its own GitHub OAuth App: one sign-in, one agent URL everywhere.

Step 1: connect GitHub in AIPx

1. In dash.aipx.run, open Integrations → GitHub → Connect and approve the MCP OAuth screen.
2. Tick extra toolsets if you need them.
3. Your agents → Create agent → MCP. Enable GitHub, set modes, save.
4. Copy https://dash.aipx.run/mcp/<agent>.

Org repos missing? New organizations restrict OAuth apps by default, so an owner has to approve AIPx.

GitHub MCP in Claude Code

claude mcp add --transport http --scope user aip https://dash.aipx.run/mcp/<agent>

Then /mcp, pick aip, sign in. No plugin needed (Claude Code MCP setup).

GitHub MCP in Cursor

No PAT header, just the URL in ~/.cursor/mcp.json (Cursor MCP):

{
  "mcpServers": {
    "aip": { "url": "https://dash.aipx.run/mcp/<agent>" }
  }
}

Connect GitHub MCP to Codex

codex mcp add aip --url https://dash.aipx.run/mcp/<agent>
codex mcp login aip

See Codex MCP.

Connect Claude to GitHub

Customize → Connectors → Add custom connector, paste the agent URL. Works in claude.ai and Claude Desktop MCP; Claude Free’s single custom connector fits all your accounts (Claude MCP connectors).

Connect GitHub MCP to GitHub Copilot

In VS Code, use GitHub Copilot Agent mode with a remote MCP server. Add the copied AIPx agent URL to .vscode/mcp.json:

{
  "servers": {
    "aipx": { "type": "http", "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

Replace AGENT_ID with your actual endpoint, complete AIPx sign-in and enable the server for the agent. Workspace policy may restrict custom servers. This is the remote MCP configuration supported by VS Code; it does not imply support on every Copilot surface. For the current setup and policy limits, see VS Code and other MCP clients. If you only need GitHub inside VS Code, a direct GitHub connection is simpler.

Direct GitHub MCP vs through AIPx

	Direct	Through AIPx
Auth in Claude Code, Cursor, Codex	PAT per client	GitHub OAuth once
Claude Desktop, claude.ai	Local Docker only	Custom connector
Scoping	Toolsets, read-only, lockdown	Plus per-tool, per-agent modes
Copilot, repo deletion tools	Available	Not available
Other services	Separate servers	Supabase MCP, Notion MCP on one URL

Scope GitHub MCP per agent

OAuth scopes set a blunt ceiling: repo means read and write on every repository you can reach, with no per-repo narrowing. AIPx skips delete_repo and admin:org, and per-tool MCP permissions decide the rest. For a single-repo agent, a fine-grained PAT connected directly fits better.

Tool	Claude Code	Cursor review	Nightly CI triage
pull_request_read, get_job_logs	Allow	Allow	Allow
issue_write	Confirm	Hide	Confirm
push_files	Confirm	Hide	Hide
actions_run_trigger	Confirm	Hide	Confirm
merge_pull_request	Hide	Hide	Hide

We talk people out of push_files on Allow: it commits straight to the remote branch, past your pre-commit hooks. Claude Code has a terminal, so let git push where you see the diff.

Confirm is a hint the client must honor, not a pause inside AIPx. Public issues can carry prompt injection, and AIPx scopes GitHub’s full toolset endpoint on its side without lockdown mode (MCP security). If tickets live in Linear MCP or Jira MCP, untick Issues. Keep Cloudflare MCP deploys on a different agent than merges. And run your first week with every write on Confirm, then promote to Allow what you approved every time.

Use a personal and a work GitHub account at once

Side projects on one account, client work on another, both in one connector labeled @login, with modes per tool × account × agent. Free: 3 accounts, 1 agent. Pro: $3/month (AIPx pricing).