MCP Server
GitHub MCP Server
GitHub's official MCP server for repository context and controlled access to issues, pull requests, Actions, security, and other GitHub APIs.
What is GitHub MCP Server?
GitHub MCP Server exposes GitHub work as configurable MCP toolsets rather than one oversized all-or-nothing integration. A client can keep the default repository, issue, pull request, user, and context tools, add focused sets such as Actions or code security, or select individual tools. The server also offers read-only mode, a local container or binary, and a hosted remote option. Those controls matter because GitHub permissions are broad: a useful installation should minimize both token scopes and the MCP tool surface enabled for the agent.
Key capabilities
Composable toolsets
Enable GitHub domains or individual tools instead of exposing the complete API surface.
Read-only enforcement
Removes write tools even when they appear in an explicitly selected toolset.
Local and remote deployment
Supports a containerized stdio server, a compiled binary, and GitHub's remote MCP service.
Use cases
Repository operations
Let an agent inspect code and coordinate issues or pull requests without leaving its MCP client.
MCP capabilities
Tools
Repositories
Read files, branches, commits, releases, and repository metadata.
Issues and pull requests
Inspect and, when permitted, manage collaboration workflows.
GitHub Actions
Query workflows, runs, jobs, and artifacts through the optional Actions toolset.
Security
Optional toolsets cover code scanning, secret protection, and advisories.
Connection and auth
- Docker or a locally built Go binary
- A GitHub token with only the permissions required by enabled toolsets
Client configuration
Generic MCP client
{"mcpServers":{"github":{"command":"docker","args":["run","-i","--rm","-e","GITHUB_PERSONAL_ACCESS_TOKEN","ghcr.io/github/github-mcp-server"],"env":{"GITHUB_PERSONAL_ACCESS_TOKEN":"${GITHUB_PAT}"}}}}