Best GitHub MCP Server in 2026: 5 Options Tested for Claude, Cursor & Cline

Table of Contents

1. What Is the GitHub MCP Server?
2. Official vs Community GitHub MCP Servers
3. The Best GitHub MCP Server Options
4. GitHub MCP Server Comparison
5. Real Workflows You Can Run Today
6. Setup: Adding the GitHub MCP to Claude
7. Token Scopes: What to Grant and What to Skip
8. Troubleshooting Common Issues
9. Frequently Asked Questions

What Is the GitHub MCP Server?

The GitHub MCP server is a Model Context Protocol server, built and maintained by GitHub, that exposes the GitHub REST and GraphQL APIs as tools an AI client can call. Once installed, your AI assistant can list repositories, open and triage issues, create branches, push commits, draft pull requests, search code across an entire organization, inspect Actions runs, and manage releases.

It runs locally as a small Node process. When Claude (or Cursor, Cline, Windsurf) starts up, the server boots alongside, registers a few dozen "tools," and waits. The AI client sends a JSON-RPC call when it needs to do something, the server hits the GitHub API, and the response flows back into the chat.

If you have never installed an MCP server before, our companion guide ranks the best desktop MCP servers for 2026. The GitHub MCP is consistently at the top of that list because it shows up in nearly every real workflow: code review, issue triage, PR drafting, repo bootstrapping, release prep.

Official vs Community GitHub MCP Servers

By 2026 there are two GitHub MCP servers worth installing for daily use, plus a few specialized community options:

• The official local GitHub MCP is the reference implementation. It runs as a Node process on your machine, reads a Personal Access Token from your config, and talks to api.github.com. Maintained by GitHub. This is what we recommend for almost everyone.
• The Remote GitHub MCP server is the hosted variant GitHub launched in 2025. It runs on GitHub-managed infrastructure, supports OAuth instead of long-lived PATs, and is the right choice for teams that do not want to manage tokens in local config files.

Beyond those two, the community has filled a few real gaps:

• GitHub Project Manager MCP for the new GitHub Projects (beta) boards
• GitHub PR Review MCP for opinionated code review workflows
• GitHub Code Search MCP for org-wide search patterns that the official MCP exposes more conservatively

Every community option in the Skiln directory has a trust score so you can see at a glance which ones are battle-tested.

The Best GitHub MCP Server Options

1. Official GitHub MCP Server

The reference implementation. Maintained by GitHub themselves. Supports both REST and GraphQL endpoints, with tools that cover repos, branches, commits, issues, pull requests, code search, Actions, releases, secrets, projects, and discussions. Authentication is a Personal Access Token, GitHub App installation token, or fine-grained PAT.

Best for: Every developer who uses GitHub daily. This is the default install we recommend in the Skiln Config Generator.

Install: npx -y @modelcontextprotocol/server-github

The MCP complements the local Git MCP, which handles on-disk git operations the GitHub MCP cannot reach.

2. Remote GitHub MCP Server (Hosted)

GitHub launched a hosted remote MCP in 2025 to remove the friction of distributing PATs across machines. Instead of running a local Node process, your AI client connects to a GitHub-managed endpoint over HTTPS and authenticates via OAuth. Same tool surface as the local server, but tokens stay on GitHub's side.

Best for: Teams managing dozens of devs, security-conscious orgs, anyone tired of rotating PATs by hand.

Install: Add the remote endpoint URL to your client's MCP config. Claude Desktop and Cursor both support remote MCPs out of the box.

3. GitHub Project Manager MCP

The official GitHub MCP supports Projects (Classic) but lags on the new GitHub Projects (beta) experience. This community MCP fills that gap with tools for board manipulation: create cards, move items between columns, filter by labels and assignees, archive completed tickets.

Best for: Teams that live in GitHub Projects boards, agile workflows that involve daily card grooming.

Install: Search Skiln for the current top-starred Project Manager MCP. The community list shifts as Projects evolves.

4. GitHub PR Review MCP

A specialized MCP designed around the code review loop. Beyond the standard pull request tools, it exposes opinionated helpers for inline comments, suggested changes, conventional-commit message rewrites, and CODEOWNERS routing.

Best for: Teams running disciplined code review, repos where PR descriptions and review comments matter as much as the diff itself.

Install: Available via npm. Check the README for the latest install command.

5. GitHub Code Search MCP

The official MCP's search tools are intentionally conservative to avoid blowing past rate limits. The community GitHub Code Search MCP exposes a richer set of search patterns including symbol search, file-path-prefix search, and language-scoped queries that mirror what github.com's search UI actually does.

Best for: Power users who need to grep across hundreds of repos in an org, security teams scanning for hard-coded secrets, anyone migrating a monorepo who needs to map references precisely.

Install: See the project README. Most variants ship as Node packages installable via npx.

GitHub MCP Server Comparison

Real Workflows You Can Run Today

The GitHub MCP earns its place in your stack the moment you stop using it for one-off questions and start running real workflows through it. Five patterns that have paid off for the Skiln team:

• Draft a PR from a working branch. "Open a PR for my current branch against main, write a description based on the commits, and assign it to Marcus." Claude pulls the commit list, summarizes the changes, opens the PR with a conventional-commit title and CODEOWNERS-aware reviewer list.
• Triage the issue queue. Ask Claude to summarize the last 20 issues in a repo. It labels them by category (bug, feature, question), flags duplicates, and proposes a triage plan in two minutes.
• Catch up on a repo after a vacation. "Walk me through what shipped in OnlineAdventuress/skiln since 2026-05-20." Claude pulls merged PRs, release notes, and the most active issues in one summary.
• Bulk close stale issues. With the GitHub MCP's search tool, find issues with no activity for 120+ days. Claude drafts a respectful "we're closing this" comment template and closes them in batch.
• Wire a release notes generator. Pull commits between two tags, group them by conventional-commit type, drop them into a markdown changelog. Pair with the git MCP for full local + remote coverage.

These patterns work in any major client. Read our best MCP clients in 2026 guide for client-specific notes.

Setup: Adding the GitHub MCP to Claude

The full install on Claude Desktop takes under a minute. Open your config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the GitHub MCP to the mcpServers object:

{   "mcpServers": {     "github": {       "command": "npx",       "args": ["-y", "@modelcontextprotocol/server-github"],       "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..." }     }   } }

Restart Claude Desktop. The new github tool should appear in the MCP sidebar with a list of available actions.

For Claude Code, use the CLI helper instead of hand-editing JSON. Read our Claude Code pricing breakdown for context on the toolchain:

claude mcp add github --env GITHUB_PERSONAL_ACCESS_TOKEN=ghp_... -- npx -y @modelcontextprotocol/server-github

Cursor and Windsurf both surface MCP installs in their settings UI; paste the same npx command and token.

The Skiln Config Generator can bundle the GitHub MCP with the local Git MCP, the Postgres MCP, Sequential Thinking, and the Filesystem MCP into a single paste-ready config.

Token Scopes: What to Grant and What to Skip

The GitHub MCP is only as safe as the token you hand it. Three rules to live by:

1. Use a fine-grained PAT, not a classic PAT, whenever possible. Fine-grained PATs let you allowlist specific repositories and grant precise permissions like "issues: read" or "pull requests: write" instead of the all-or-nothing repo scope.
2. Default to read-only. For browsing, search, and review workflows, a token with contents: read, metadata: read, issues: read, and pull_requests: read is enough. You can layer write scopes later.
3. Separate write tokens. When you do need write access (push, open PR, merge), generate a second token used only for those flows. Store it under a different env var so accidental tool calls do not pick it up.

If you work across multiple orgs, generate one PAT per org and connect them as named MCP servers (e.g. github-personal, github-work). Claude can route tool calls to the right token based on the org name in your prompt.

Pair this with the security guidance in our Git MCP guide.

Troubleshooting Common Issues

The five problems we see most often when developers install the GitHub MCP:

• "Bad credentials" on every call. The token is wrong, expired, or revoked. Generate a fresh PAT, paste it into config, restart the client.
• 403 rate limit. Hit the 5,000 requests per hour ceiling. Either back off, switch to a GitHub App installation token (15,000/hour), or move heavy automation to the Remote GitHub MCP.
• "Repository not found" on a real repo. Token scope does not include that repo. With a fine-grained PAT, double check the repository allowlist. With a classic PAT, ensure the repo scope is granted.
• MCP does not appear in the sidebar. Client failed to start the server. Check the client logs for the actual error. Most often: Node not installed, or npx pulling from a stale cache. Run npx clear-npx-cache and retry.
• Tools register but every call hangs. Network blocked api.github.com or the npx process is stuck on certificate verification. Try setting NODE_TLS_REJECT_UNAUTHORIZED=1 and retest, or run the same command directly in a shell to surface the error.

Frequently Asked Questions

What is the GitHub MCP server?

The GitHub MCP server is a Model Context Protocol server maintained by GitHub that connects AI assistants like Claude Desktop, Claude Code, and Cursor to the GitHub API. Once installed, the AI can read repositories, manage issues, open pull requests, search code across orgs, trigger GitHub Actions, and inspect release artifacts. It is free, open source, and runs as a local process that talks to api.github.com on your behalf.

Is the GitHub MCP server free?

Yes. The GitHub MCP server itself is free and open source. Usage counts against your normal GitHub API rate limits (5,000 requests per hour for authenticated PATs, 15,000 for GitHub Apps), so heavy automation may bump into limits even though the server software costs nothing.

Do I need a Personal Access Token?

Yes. The GitHub MCP requires a Personal Access Token, GitHub App installation token, or OAuth token. PATs are the simplest path for individuals. For team settings, prefer GitHub App tokens with fine-grained permissions so you can scope access per repo. Never share PATs across machines or commit them to a repo.

Can the GitHub MCP server write to my repositories?

Yes, if the token has the right scopes. With repo:write access, the AI can create branches, push commits, open pull requests, and merge them. The safest pattern is to issue two tokens: one read-only PAT for browsing and code review, and a second write-scoped token used only in flows you have explicitly authorized.

Does the GitHub MCP work with private repos?

Yes, as long as your PAT or GitHub App token has access to those repos. Fine-grained PATs let you allowlist specific repositories, which is the recommended setup for client work or sensitive codebases.

What is the difference between the GitHub MCP and a Git MCP?

The Git MCP operates on your local .git folder. It runs commands like git status, git diff, git log, git add, and git commit on a repo you have cloned. The GitHub MCP talks to the GitHub API instead, so it can do everything that happens on github.com: pull requests, issues, search across orgs, Actions, releases. Most developers install both side by side and let Claude pick the right tool per request.

Will the GitHub MCP server merge a PR without asking?

Only if you tell it to. The MCP itself exposes merge as a tool; the AI client decides whether to call it. Claude Desktop will always prompt you before calling write tools by default. Claude Code can be configured with auto-approve rules, so be conservative when adding write tools to that allowlist.

Where can I browse all GitHub-related MCP servers indexed on Skiln?

Visit /mcps and filter for 'github' or 'version-control'. As of 2026, Skiln tracks 600+ git and GitHub related MCP entries across PulseMCP, Smithery, Glama, LobeHub, OpenClaw, and mcp.directory.

Last updated: June 10, 2026 · Skiln tracks GitHub MCP and related releases daily across 13 source registries.