MCP server for GitHub
TL;DR
A GitHub MCP server gives a coding agent access to repositories, issues, and pull requests through tools. Select one by documented capability and the access it requires, preferring read-only operation for review tasks.
Capabilities
GitHub servers typically expose repository data, issue and PR operations, and search. Whether they can modify resources (open PRs, edit issues) depends on the implementation and its permissions.
Permissions
A token with broad scope grants the agent wide reach. Prefer a token limited to the repositories and operations the task needs, and prefer read-only tokens where the task is review.
In this collection
- Best MCP servers →
- How to choose an MCP server →
- Verified MCP servers →
- MCP server comparison methodology →
- MCP registries, directories, and marketplaces →
- MCP servers for databases →
- Read-only database access with MCP →
- MCP servers for developers →
- MCP browser automation →
- MCP servers for search and research →
- MCP servers for productivity →
- MCP servers for DevOps and cloud →
- Enterprise MCP →
- Postgres MCP server guide →
- Playwright MCP →
- MCP server not showing in Claude Desktop →
- Cursor MCP tools not showing →
- MCP connection refused and timeout errors →
- Claude Desktop MCP configuration →
- VS Code MCP configuration →
- Remote MCP servers with OAuth →