MCP server · Developer tools

OfficialSource ValidatedRead-writeMITUpdated August 2026

GitHub MCP Server

GitHub's official MCP server: repositories, issues, pull requests, code search and Actions as tools — hosted remotely or run locally in Docker.

InstallSource repository

Quick verdict

If you use any MCP-capable client with GitHub, this is a first install. Run it read-only first, then widen the toolsets deliberately.

  • MaintainerGitHub (official)
  • Security scopeRead-write
  • Transportsstdio, streamable-http
  • Install channeldocker · ghcr.io/github/github-mcp-server
  • EvidenceSource Validated
  • LicenseMIT · Open source

GitHub's official Model Context Protocol server. It exposes repositories, issues, pull requests, comments, code search, Actions runs, Gists and more as structured tools, in both read and write directions, so an agent can read an issue, search code, open a pull request or leave a review without leaving the editor. Two supported paths: the hosted remote server at https://api.githubcopilot.com/mcp/ (GitHub OAuth by default, or a personal access token; no local process) and the local server as the Docker image ghcr.io/github/github-mcp-server, authenticated with GITHUB_PERSONAL_ACCESS_TOKEN. There is no npm package; a binary can be built from source with go build. Toolsets are selected with --toolsets (or GITHUB_TOOLSETS; a default set applies if none is named) and --read-only skips every write tool.

MCP security best practices

Install GitHub MCP Server

docker run -i

Config entry (mcpServers)
{
  "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_PERSONAL_ACCESS_TOKEN>"
      }
    }
  }
}

Docker installed and running for the local server. The hosted remote server (https://api.githubcopilot.com/mcp/) needs no local process and signs in with GitHub OAuth. No npm or npx package exists; go build from source is the other local path.

Credentials

NameRequiredWhat it is for
GITHUB_PERSONAL_ACCESS_TOKENRequiredA fine-grained personal access token scoped to only the repositories and permissions the agent needs. The hosted remote server can use GitHub OAuth instead of a token.

Verified configurations

Not run by us yet. This profile is Source Validated: the install channel, config entry, credentials and license were checked against the source and upstream metadata, but no configuration has been installed, discovered and executed in a recorded environment. When one is, it appears here with the eight scope dimensions below.

Best for

Developers who want the agent to read issues, search code and open or review pull requests directly — with the official server rather than a third-party wrapper.

Why use it

It is the authoritative bridge between agents and GitHub, maintained by GitHub's own engineers, so it tracks API and auth changes at the source. Toolsets keep the tool list small, --read-only gives a safe first run, and the hosted remote path means nothing to install for clients that support remote servers.

Tradeoffs

Write tools are real and immediate — an agent can open issues, comment and push changes — so start with --read-only, scope the token tightly and keep approval prompts on. It needs the GitHub API, so there is no offline or air-gapped mode, and the local path needs Docker (or a Go toolchain).

Upstream state

repository active · in the official MCP Registry (active). Lifecycle is derived from a committed upstream snapshot at build time, never authored by hand.

Official MCP Registry name: io.github.github/github-mcp-server

Editorial review

Reviewed byOpenSourcesAI EditorialLast updatedAugust 2026Sourcesgithub/github-mcp-server README — remote server URL and auth, Docker config, --toolsets/GITHUB_TOOLSETS, --read-only; Official MCP Registry entry io.github.github/github-mcp-server

Grade B — Source Validated. Re-review is due by 2027-02-16. Config entries, credential names and package status can change upstream; verify against the source repository before granting an agent access.

Sources

  • Hugging Face MCPSearch Hugging Face models, datasets, Spaces, papers and docs through MCP, with optional Hub and compute tools.
  • Semgrep MCPRun Semgrep security scans through MCP so coding agents can analyze source code for vulnerabilities locally.
  • Sentry MCPInspect errors, traces and issues, then perform scoped issue triage through Sentry's official MCP service.

Related guides

All MCP servers →