Developer · Remote MCP server
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.github/github-mcp-server- Version
- 1.13.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- github (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/github) · how
- Listed under
- GitHub MCP servers
- Repository
- github.com/github/github-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.githubcopilot.com/mcp/ | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/github/github-mcp-server:1.13.0 | - | stdio |
How to connect GitHub
GitHub is a remote MCP server: there is nothing to install. Its endpoint is https://api.githubcopilot.com/mcp/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/github/github-mcp-server:1.13.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/github/github-mcp-server:1.13.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"github-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/github/github-mcp-server:1.13.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| GithubManage repositories, users, releases, and automate GitHub workflows. | Local · stdio |
| GitHubGitHub via MCP: search, repos, issues, PRs, files, notifications. OAuth device flow or token. | Local · stdio |
| GitHubConnect AI assistants to GitHub - manage repos, issues, PRs, workflows, and git operations. | Local · stdio |
| GithubGitHub MCP Server - List PRs, issues, repo info, and search code. | Local · stdio |
| GithubGitHub MCP - wraps the GitHub public REST API (no auth required for public endpoints) | Remote · HTTPLive check: ✓ handshake |
| GithubGitHub analytics - repos, PRs, issues, releases, contributors. | Local · stdio |
| Github ActionsGitHub Actions MCP - view runs, read logs, re-run jobs, and manage CI/CD. | Local · stdio |
| GitHub Actions AuditGitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection. | Remote · HTTPLive check: sign-in required |