How to Connect the GitHub MCP Server to Claude Code

Let Claude Code read issues, review pull requests, and search code across your GitHub repositories through a remote MCP server.

8 minIntermediate

Visit Claude Code

The GitHub MCP server lets Claude Code reach into your repositories to read issues, inspect pull requests, search code, and more, without you copy-pasting URLs into the chat. GitHub hosts a remote version you can connect over HTTP, which means there is nothing to install locally. This guide connects it and authenticates with OAuth.

A GitHub account with access to the repos you care about
Claude Code updated to a recent version that supports remote MCP
A browser available to complete the OAuth flow

Step 1: Add the remote server URL

Remote servers are added with the transport flag set to http and the hosted endpoint as the target. The GitHub server is published at the address below.

terminal

claude mcp add --transport http github https://api.githubcopilot.com/mcp/

Step 2: Authenticate from inside Claude Code

Remote servers that require login use OAuth. Start a session and run the auth command for the server. Claude Code opens your browser, you approve access, and the token is stored for you. You never paste a personal access token into a config file.

claude - my-project

$/mcp

github needs authentication

Select github, then choose Authenticate

Opening browser to complete OAuth...

github connected

Claude Code - /mcp

MCP Servers

filesystem connected

github connected (OAuth)

Press a number to manage a server

The /mcp panel lists each server and its auth state.

Step 3: Try a real query

Once connected, ask Claude Code to work with your repository data. It will call the GitHub tools and bring back live results rather than relying on stale memory.

Claude Code

You

List the 5 most recently opened issues in my-org/web with the bug label.

Agent

Here are the latest 5 bug issues: #482 crash on upload, #479 dark mode flicker, #477 broken redirect, #475 slow search, #470 stale cache. Want a summary of any?

Mind the permissions you grant

During OAuth you authorize the server to act on repos you can see. Approve only what you need and review the granted scopes. You can revoke access later from your GitHub account settings.

Step 4: Confirm and reconnect if needed

If the server ever shows as needing authentication again, just open the /mcp panel and re-authenticate. Tokens can expire, and switching machines means a fresh login.

Result: Claude Code can now read and search your GitHub repositories live, so you can ask about issues and pull requests in plain language and get current answers.