MCP server · Code and developer tools
GitHub MCP server
Lets an assistant read code, manage issues and pull requests, and check Actions runs in the GitHub repositories you can access.
- Maintainer
- GitHub (official)
- Licence
- MIT
- Runs
- Remote (URL)
- Sign-in
- OAuth sign-in in the app
- Registry version
- 2.0.2 (updated 2026-10-08)
- Last activity
- 2026-10-13
Overview
What it does
GitHub’s own MCP server connects an assistant to the GitHub API. GitHub hosts a remote version at api.githubcopilot.com that signs you in with OAuth or accepts a personal access token in an Authorization header. A local version runs as a Docker image (ghcr.io/github/github-mcp-server) or a Go binary, and reads a token from GITHUB_PERSONAL_ACCESS_TOKEN or signs you in through the browser on first use.
Tools are grouped into toolsets such as repos, issues, pull_requests, actions, code_security, dependabot, discussions, projects and governance. Only context, repos, issues, pull_requests and users load by default, which keeps the tool list short. Pick it when you want an assistant to triage issues, review or open pull requests, or explain a failing workflow without leaving the editor. Extra toolsets are switched on with a flag, an environment variable or a URL path, and adding /readonly to any remote URL exposes read tools only. GitHub Enterprise Server and ghe.com hosts are supported with the local server.
Tools
What the assistant can do
- Browse repositories, files, branches and commits
- Create, update and comment on issues
- Open, review and merge pull requests
- List GitHub Actions workflows, runs and job logs
- Read code scanning, secret scanning and Dependabot alerts
- Work with Discussions, Gists, Projects and notifications
- Manage repository rulesets and custom properties (governance toolset)
Install
Install GitHub MCP server in your app
You need:
- A GitHub account
- An MCP client with remote server support (OAuth needs a client that has registered a GitHub or OAuth app; any remote-capable client can use a personal access token instead)
- Docker, only if you run the local server
Run in your project. --scope local keeps the servers private to you in this project; use user for every project.
claude mcp add --scope local --transport http github https://api.githubcopilot.com/mcp/
Project root. Commit it to share the servers with your team; each person sets the variables in their own shell.
{
"mcpServers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/"
}
}
}
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json (Settings → Developer → Edit Config). Restart Claude after saving.
{
"mcpServers": {}
}
- github is a remote server: add it as a custom connector (Customize → Connectors → + Add → Add custom connector; on Team and Enterprise plans an owner adds it under Organization settings → Connectors), with the URL https://api.githubcopilot.com/mcp/.
- GitHub’s own guide says its remote server can’t sign in from Claude Desktop yet and recommends its local Docker server there instead.
In your project, or ~/.cursor/mcp.json for every project.
{
"mcpServers": {
"github": {
"url": "https://api.githubcopilot.com/mcp/"
}
}
}
In your workspace. VS Code asks for each secret the first time a server starts and stores it securely.
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/"
}
}
}
macOS/Linux: ~/.config/devin/mcp_config.json · Windows: %APPDATA%\devin\mcp_config.json. Read by the default Devin Local agent and by the legacy Cascade agent.
{
"mcpServers": {
"github": {
"url": "https://api.githubcopilot.com/mcp/"
}
}
}
Want it alongside other servers? Open GitHub MCP Server in the MCP config generator and add the rest; it writes one file per app. The snippets follow the setup in the server’s README, checked on 2026-10-14.
Before you install
- With the default toolsets the assistant can create issues, comment, and open or merge pull requests in any repository your account can write to. Use a fine-grained token limited to the repositories and permissions you need.
- For read-only use, add /readonly to the remote URL, or run the local server with --read-only (GITHUB_READ_ONLY=1 in Docker).
- Issue, pull request and comment text from public repositories can carry prompt injection. Lockdown mode (--lockdown-mode or GITHUB_LOCKDOWN_MODE=1) filters content from people without push access, but GitHub notes it is not an access boundary.
- A remote server sees whatever the assistant sends it. Sign in with the narrowest access the service offers. See how to choose a safe server.
Why it’s listed
Why we list it
The vendor’s own server for the most widely used code host, with toolsets and read-only and lockdown modes that let you scope what an assistant can do.
Related
More MCP servers
- GitLab MCP serverGives an assistant access to GitLab projects, issues, merge requests, pipelines and search through an MCP endpoint built into GitLab.
- Sentry MCPLets a coding assistant search Sentry errors, traces and logs, triage issues and read Sentry docs while you debug.
- Figma MCP serverGives a coding assistant design context from Figma files, such as layout, variables and components, and can write back to the canvas.
- Semgrep MCP serverLets an assistant scan code for security issues with Semgrep, write custom rules and pull findings from Semgrep AppSec Platform.
- SonarQube MCP ServerConnects an assistant to SonarQube Cloud or Server to analyse code, review issues and hotspots, and check quality gates.
- Postman MCP ServerConnects an assistant to your Postman workspaces, collections, specs and environments, and can generate client code from APIs.
All MCP serversMCP config generatorGuide: MCP servers in Claude CodeGuide: what is MCP?