6 Aug 2026·1 min read
Set up GitHub MCP Server with scoped tokens
GitHub MCP connects agents to repositories, issues, pull requests, and Actions—with scope-controlled access. This guide walks through Docker-based setup so you can start read-only before enabling write tools.
What GitHub MCP Server is
GitHub MCP Server is GitHub’s official MCP integration. With the right token scopes, an agent can search code, inspect files, triage issues, and review pull requests without copying repository context into chat.
Install command
docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-serverSetup steps
- Create a fine-grained personal access token with the smallest required repository scopes.
- Store the token in your MCP client’s secure environment configuration—never in committed files.
- Register the Docker command in Cursor, Claude Code, or VS Code MCP settings.
- Start in read-only mode; enable issue or PR write tools only when a workflow requires them.
Security notes
Token scopes define what the agent can read or change. Prefer organization-scoped fine-grained tokens over classic full-access PATs. Review GitHub audit logs after first use.
Compare more dev workflows in the MCP Servers Directory, Playwright MCP setup, and Systematic Debugging skill.
FAQ
- Does GitHub MCP require Docker?
- Bowora lists the official container image; other transports may exist upstream.
- Can the agent modify my repositories?
- Only if the token scopes allow it. Start read-only and expand deliberately.
- Which clients does Bowora list?
- Claude, Codex, Cursor, and VS Code.
- Where is the source?
- Linked from /mcp/github-mcp-server.
mcpgithubdockersetup
