How to Install GitHub MCP in Claude Code (Remote or Local)

The Short Answer

To install GitHub MCP in Claude Code, create a GitHub personal access token, then run claude mcp add --transport http github https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer $GITHUB_PAT", start claude and check that github shows a checkmark in /mcp. That connects GitHub's official hosted server, so there is nothing to install or keep updated.

If you would rather not manage a token, run the server locally with Docker instead: on first use it opens a GitHub login in your browser and keeps the token in memory only. Both options use the official GitHub MCP server from github/github-mcp-server.

Remote or Local?

Most people should start with remote. Choose local when you want OAuth instead of a long-lived token, need GitHub Enterprise Server, or must keep traffic on your machine.

Prerequisites

• Claude Code installed. Open it inside your project directory so the configuration is scoped clearly, as GitHub's own guide recommends.
• A GitHub personal access token for the remote server or a PAT-based local setup. Create one at github.com/settings/personal-access-tokens/new.
• Docker, installed and running, for the local Docker option.

Creating the token

Grant only what you need. GitHub's README lists these classic scopes as a baseline:

With a fine-grained token, pick the specific repositories and the permissions that match the toolsets you plan to enable. Your organization may also restrict or require approval for PATs. Use separate tokens per project, rotate them, and never commit them.

Keep the token out of your shell history by putting it in an environment variable or a gitignored .env file:

export GITHUB_PAT="your_token_here"   # placeholder, not a real token

Option 1: Remote Server (Recommended)

Step 1: Add the server

The form from the Claude Code MCP docs:

claude mcp add --transport http github https://api.githubcopilot.com/mcp/ \
  --header "Authorization: Bearer $GITHUB_PAT"

GitHub's Claude install guide uses add-json for Claude Code 2.1.1 and newer:

claude mcp add-json github \
  '{"type":"http","url":"https://api.githubcopilot.com/mcp","headers":{"Authorization":"Bearer '"$GITHUB_PAT"'"}}'

Both save the same thing. Your shell replaces $GITHUB_PAT with the real value before Claude Code sees it, so the token is stored in Claude Code's config, not the variable name.

Step 2: Choose a scope

For project scope, never paste the token into .mcp.json. Claude Code expands environment variables in that file, so commit this instead and let each teammate set GITHUB_PAT themselves:

{
  "mcpServers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/",
      "headers": {
        "Authorization": "Bearer ${GITHUB_PAT}"
      }
    }
  }
}

What about OAuth on the remote server?

GitHub's README notes that OAuth on the remote server requires each host app to have a registered GitHub App or OAuth App, and that any host supporting remote servers can use PAT authentication. GitHub's Claude guide therefore uses a PAT. If you want browser login instead of a token, the local server below has OAuth built in.

Option 2: Local Server with Docker

OAuth login (no token)

The official image ships with GitHub's OAuth app credentials, so on github.com you provide nothing. Publish a fixed callback port to loopback:

claude mcp add github -e GITHUB_OAUTH_CALLBACK_PORT=8085 -- \
  docker run -i --rm -p 127.0.0.1:8085:8085 \
  -e GITHUB_OAUTH_CALLBACK_PORT ghcr.io/github/github-mcp-server

On the first tool call the server opens GitHub's authorization page. The token is kept in memory only, so expect to sign in again after the server restarts.

With a PAT

A PAT takes precedence over OAuth:

claude mcp add github -e GITHUB_PERSONAL_ACCESS_TOKEN=$GITHUB_PAT -- \
  docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server

Note where -e appears: once before -- (Claude Code sets the variable) and once inside the docker run command (Docker passes it into the container).

Without Docker: the release binary

Download a binary from the releases page and put it on your PATH. With an official build, OAuth needs no flags and picks a random loopback port:

claude mcp add github -- github-mcp-server stdio

Or with a PAT, as GitHub's guide shows:

claude mcp add-json github \
  '{"command":"github-mcp-server","args":["stdio"],"env":{"GITHUB_PERSONAL_ACCESS_TOKEN":"YOUR_GITHUB_PAT"}}'

Toolsets, Read-Only and Lockdown

By default the server enables the context, repos, issues, pull_requests and users toolsets. Enabling only what you need helps Claude pick the right tool and keeps context small. Other toolsets include actions, code_security, dependabot, discussions, gists, notifications, orgs, projects, labels and more; all enables everything.

A read-only remote setup limited to repos, issues and pull requests, as a .mcp.json entry:

{
  "mcpServers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/",
      "headers": {
        "Authorization": "Bearer ${GITHUB_PAT}",
        "X-MCP-Toolsets": "repos,issues,pull_requests",
        "X-MCP-Readonly": "true"
      }
    }
  }
}

Lockdown mode hides content in public repositories from authors without push access. It is a best-effort filter against prompt injection from untrusted issues and comments, not a security boundary, but it is worth turning on when Claude reads public repos. See MCP security best practices.

Verify the Connection

claude mcp list
claude mcp get github

Inside a session, /mcp should show github with a checkmark. claude mcp add does not validate credentials, so a wrong token is accepted at add time and only fails here, with a 401 in the failure detail.

Example Prompts

• "List the open pull requests in this repo and summarize what each one changes."
• "Read issue 123, find the code it refers to, and propose a fix."
• "Why did the latest GitHub Actions run on main fail? Show me the failing step."
• "Create a branch, commit the changes we just made, and open a draft PR that links issue 123."
• "Review PR 45 and leave comments on anything that looks risky."
• "Are there open Dependabot or code scanning alerts in this repo?"

The last two need the actions, dependabot or code_security toolsets enabled, plus matching token permissions.

Troubleshooting

Do you already use the gh CLI? Claude Code can call it through the shell, and it handles many tasks without MCP. The MCP server earns its place when you want structured tools, toolset limits, read-only mode and lockdown instead of open shell access.

Next Steps

With GitHub connected, add servers that feed it work: Playwright MCP to verify a fix in the browser before opening the PR, or Supabase MCP for database changes. Browse more developer tools in the MCP server directory, and see the Claude Code MCP guide for scopes, OAuth and managing servers.