What it does

Exposes a wide set of GitHub operations as MCP tools — listing repos, reading files, searching code, opening issues, drafting PRs, reading workflow runs, and more. Probably the most-installed MCP server in 2026.

Why you’d install it

If your agent reads or writes code, github-mcp-server is the path of least resistance. The alternative — wiring octokit.js calls into a custom tool layer — duplicates work that GitHub now maintains officially.

Setup

1. Generate a PAT (classic or fine-grained). Pick the smallest scope that covers your use case.
2. Install the server:

   # Claude Desktop (config.json under "mcpServers")
   "github": {
     "command": "npx",
     "args": ["-y", "@github/mcp-server"],
     "env": { "GITHUB_TOKEN": "ghp_..." }
   }

3. Restart Claude Desktop or your MCP host. Tools appear under “github”.

My take

Pending Sush’s real usage notes. Structure here reflects public information.

For reading and exploring repos — fine. For writes — always pair with a human-in-the-loop step until you’re confident. Don’t grant delete_repo scopes lightly.

Combinations

Works especially well with:

• filesystem-mcp — for local + remote unified file access
• slack-mcp — to post PR summaries to channels
• playwright-mcp — to verify deployed previews

Used in recipes:

• Automate YouTube SEO (peripheral)