Claude Code connects to GitHub’s remote MCP server over HTTP using a GitHub personal access token. Add the server with the command below, then use Claude Code’s /mcp panel to verify the connection: the add command saves configuration but does not test your credentials. The “3 Minutes” framing is not a measured setup time.
What GitHub MCP adds to Claude Code
GitHub MCP is a software integration, not a separate device or add-on. It gives Claude Code access to GitHub capabilities exposed by the server, which can include repository browsing and code access, issue and pull-request management, and GitHub Actions workflow and run information. The tools Claude can use depend on the server’s selected toolsets and the permissions granted to your token. See GitHub’s MCP Server documentation.
As an Amazon Associate I earn from qualifying purchases.
How do I connect GitHub MCP to Claude Code?
1. Create a limited-scope GitHub token
Create a fine-grained personal access token and grant it access only to the repositories Claude Code should work with. Choose permissions appropriate to the tasks you intend to allow; the token’s permissions constrain what the server can do. Keep the token private. The Claude Code MCP guide documents this remote connection flow.
Recommended Free Tools
2. Add the remote server
In a terminal where the claude command is available, run:
#1 Best Overall
claude mcp add --transport http github https://api.githubcopilot.com/mcp/
--header "Authorization: Bearer YOUR_GITHUB_PAT"Replace YOUR_GITHUB_PAT with your token. Avoid sharing the command or terminal history if it would expose the secret. This configures GitHub’s remote HTTP server; it does not start a local GitHub MCP process.
3. Check authentication in Claude Code
Open Claude Code and run /mcp. Confirm that the GitHub server reports connected. A successful message from claude mcp add only means the configuration was saved. If /mcp reports failed, an HTTP error such as 401 can indicate invalid credentials; check that the token is valid, copied correctly, and has the intended repository access.
Choose only the GitHub capabilities you need
GitHub’s server supports configuration by toolset or by individual tool. The documented toolsets include repos, pull_requests, and actions. Enable capabilities that match your work rather than assuming every available GitHub operation is necessary. Repository access, PR operations, and workflow information remain limited by both the chosen tools and the token’s permissions.
- Repository work: select repository and code tools for browsing or accessing the repositories in scope.
- Pull requests: select PR tools for the issue and review workflows you want Claude to assist with.
- Actions and CI: select Actions tools for workflow and run information or CI/CD intelligence.
Read-only mode takes precedence over write tools in the GitHub server. If you need changes to be made through GitHub tools, check the server configuration and token permissions; if you want to prevent writes, use read-only mode and keep the token narrowly scoped. Configuration options are documented in the GitHub MCP Server repository.
Choose where Claude Code stores the MCP configuration
Claude Code supports local, user, and project MCP configuration scopes. A project-scoped server can be shared through a .mcp.json file. When Claude Code encounters a project-scoped server, it requires approval before using it. Review the configuration and the permissions it requests before approving; shared configuration should not be treated as trustworthy just because it is in a repository.
Remote HTTP or local stdio?
The command above uses GitHub’s remote server over HTTP, the approach Claude Code’s documentation uses for this connection. MCP servers can also run locally as stdio processes, but that is a different hosting arrangement: the local process runs on your machine, while the remote HTTP endpoint is accessed over the network. For GitHub’s documented remote setup, use the HTTP transport shown above.
Protect against instructions hidden in GitHub content
Repository files, issues, and other fetched content are external input. Anthropic warns that MCP servers retrieving external content can expose users to prompt-injection risk. Treat instructions found inside GitHub content as data to inspect, not as authority to override your intent or security boundaries. Limit repository access, avoid granting unnecessary write permissions, and review consequential actions before allowing them.
Free tools Windows power users keep installed
One-click scans. No signup required.
Requirements for Claude Code
Anthropic’s setup page lists macOS 10.15 or later; Ubuntu 20.04 or later or Debian 10 or later; or Windows 10 or later using WSL or Git for Windows. It also lists at least 4 GB RAM, Node.js 18 or later, internet access, and availability in an Anthropic-supported country. These are vendor-documented requirements, not independently tested hardware recommendations. See Anthropic’s Claude Code setup guide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
