Connects AI tools to GitHub so agents can read repositories and code, manage issues and pull requests, analyze code and automate workflows. Available as a remote server hosted by GitHub or a local Docker server.
What it does
Where GitHub MCP Server runs and what it adds, from its documentation
Browse and search repositories, code and commits
Create, update and manage issues and pull requests
Monitor GitHub Actions runs and manage releases
Review code security findings and Dependabot alerts
Access discussions and notifications
Limit tools with toolsets via --toolsets or --tools
When to use it
Good fit
Giving an agent GitHub context from VS Code, Claude, Codex, Cursor or Windsurf
Triaging issues and reviewing PRs in natural language
Debugging CI failures
Not for
Hosts without remote MCP support, unless you use the local Docker server
Setups where broad token scope is not acceptable
How to install GitHub MCP Server
You need: MCP host with remote server support (e.g. VS Code 1.101+, Claude Desktop, Cursor, Windsurf); Docker for the local server (image ghcr.io/github/github-mcp-server); GitHub OAuth login or personal access token
Pick the remote server (https://api.githubcopilot.com/mcp/) or the local Docker server
Follow the install guide for your host (Claude, Codex, Cursor, Windsurf, VS Code and others are linked in the README)
Authenticate with OAuth or a GitHub personal access token
How do I connect GitHub MCP Server to Claude Code or Cursor?
Use the host-specific guides linked in the README (docs/installation-guides), pointing at the remote URL https://api.githubcopilot.com/mcp/ or the local Docker server. source
Does GitHub MCP Server need a personal access token?
Not necessarily; OAuth is supported, but a PAT can be used and takes precedence if GITHUB_PERSONAL_ACCESS_TOKEN is set. source
Can I limit what GitHub MCP Server exposes?
Yes, with the --toolsets flag or GITHUB_TOOLSETS variable, and --tools for single tools. source