Home / Directory / GitHub MCP Server
GitHub's official MCP: issues, PRs and Actions, with a read-only switch
If the agent should open a PR or read an Actions log without a brittle gh scrape, this is the first-party server. It is also an easy way to let an agent rewrite a repository you did not intend to hand over.
What it does
The server talks to GitHub: repositories, issues, pull requests, Actions, code search and security features, grouped into toolsets. You can run a local binary or use the hosted remote at GitHub's Copilot MCP URL, with OAuth or a personal access token.
A read-only mode drops write tools. That is the setting we would start with. Full write access means the agent can comment, label, open PRs or otherwise mutate the org, subject to the token's scopes.
This is not the archived community GitHub server in modelcontextprotocol/servers. GitHub maintains this one.
Who it is for
Teams whose coding agent already lives in GitHub PRs. Useful for "summarize the failing workflow" and "draft a PR from this branch" if you accept the write path.
Skip it on a machine that also has a broad PAT in the environment and no human approval on tools. The failure mode is an agent that "helps" by commenting on twenty issues.
Our take
Official and MIT is the right default for GitHub access. Toolsets and read-only are the controls that matter.
Limits: hosted MCP still means GitHub sees those tool calls. A PAT with repo scope is a credential; treat the MCP config like you treat .env. The server will not teach the agent your review standards.
We have no affiliation with GitHub beyond using the product.
Compared with AgentKit Drawer
Our kits never open PRs for you. They tell the agent how to write the diff. GitHub MCP is a platform connector.
No pack CTA. If you want review behavior, look at the Agent Builder pack's PR-reviewer prompt or the Claude Code code-reviewer subagent, and keep this server read-only until you need a write.