---
title: "GitHub MCP Server: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/github/
description: "Connects an assistant to repository, issue, pull-request and workflow operations with selectable toolsets and account permissions."
---

# GitHub MCP Server: review, setup & limitations · Undominated.ai

> Connects an assistant to repository, issue, pull-request and workflow operations with selectable toolsets and account permissions.

[← Explore all mcp servers](/mcp-servers/)

REPOSITORY COLLABORATION / GitHub

# GitHub MCP Server

Connects an assistant to repository, issue, pull-request and workflow operations with selectable toolsets and account permissions.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/github/github-mcp-server)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher GitHub
 Licence [MIT ↗](https://github.com/github/github-mcp-server/blob/c59e8c199efbf14467211861de44afaeeb6873e3/LICENSE)
 Revision c59e8c199efb
 [Read what was—and wasn’t—checked ↓](#review)

“The GitHub MCP Server connects AI tools directly to GitHub's platform.”

 [GitHub · upstream description ↗](https://github.com/github/github-mcp-server/blob/c59e8c199efbf14467211861de44afaeeb6873e3/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Offers a publisher-hosted endpoint and a separately inspectable local implementation.
- Toolset selection, read-only mode and OAuth/PAT/GitHub App paths allow a deployment to match a defined repository task.
- The pinned README connects agents to repositories, issues, pull requests, and Actions through a hosted remote server or a local process.
- Read-only mode drops write tools, and lockdown mode is documented as a content filter rather than a change to what the GitHub credential can do.

### A good fit for

 - Reviewing a pull request together with its issue discussion before drafting a change.
- Finding repository files and comparing pull-request changes using a token scoped to the required repositories.
- Reading GitHub repositories, issues, and pull requests with a token whose scopes you choose
- Refusing cleartext GitHub Enterprise hosts except loopback

### Weigh up before choosing

 - Write-capable toolsets can change repositories, issues, pull requests and workflows; read-only mode is an explicit configuration choice.
- Remote OAuth compatibility and organization policies vary by MCP host; the repository licence does not replace GitHub service terms.
- Lockdown is a best-effort filter on selected public-repository content, not an authorisation boundary. Private repositories are unaffected and documented trusted bots bypass the author filter.
- Read-only mode removes write tools; it does not reduce the token permissions or make issue text trustworthy.
- GitHub Enterprise Server cannot use the hosted remote MCP endpoint.
- Lockdown mode does not change what the underlying credential can read or write, and trusted bot accounts are exempt.
- A personal access token or OAuth login is required for the local server, and non-HTTPS enterprise hosts are refused.
- A pin does not verify transitive dependencies.
- This review did not execute the resource.
- Fine-grained PAT tools can remain visible even when the token cannot invoke them; discovery is not authorization.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - README.md setup, configuration and operating-limit sections at c59e8c199efbf14467211861de44afaeeb6873e3
- LICENSE at the same revision
- cmd/github-mcp-server/main.go
- README.md
- LICENSE
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The local Docker example combines documented read-only, lockdown and toolset options; credentials are inherited rather than written into the example.
- Lockdown checks authors on selected public-content tools and can leave the same content accessible through other tools or the GitHub API.
- The README says the server reads repositories and code, manages issues and pull requests, and watches Actions, either at the hosted GitHub endpoint or as a local Docker or binary process.
- `--read-only` offers only read-only tools so the server will not modify repositories, issues, or pull requests.
- Lockdown mode filters public-repository content from authors without push access, but the same README says it is not an authorization boundary and that content can still be reached with the same credential.
- GitHub Enterprise Server does not support remote hosting, and a non-HTTPS enterprise host is refused except for a loopback address.
- Commit search only searches commit messages on the default branch; an unscoped query can match across GitHub.

### Not established by this review

 - Server startup, authentication and live tool calls were not tested.
- Published package/container parity with the inspected source commit and security isolation were not tested.
- The server was not started and its tools were not called.
- A pin does not verify transitive dependencies.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/github/github-mcp-server/blob/c59e8c199efbf14467211861de44afaeeb6873e3/README.md)
 - For VS Code, add the documented remote-server configuration and complete the GitHub OAuth consent flow.
- For another client, use its linked installation guide; confirm toolsets and account policy before allowing writes.

### Before you start

 - A GitHub account with access to the target repositories.
- An MCP host supporting the selected remote authentication path, or the documented local runtime.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "servers": {
 "github": {
 "type": "http",
 "url": "https://api.githubcopilot.com/mcp/"
 }
 }
} Copy configuration ↗

### Compatibility

Remote-capable MCP clients; the example below is specifically VS Code configuration. · Local stdio clients using the documented binary or container.

### Implementation

Go

### Transports

stdio · Streamable HTTP

### GitHub account / OAuth or token

 - Reads private repository content allowed by the authenticated identity.
- Enabled tools may create or modify issues, pull requests, files, releases and workflows.

### Cost model

GitHub account entitlements and API/service limits apply; the local source licence does not include a model subscription.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned upstream setup, capabilities and operating limits ↗](https://github.com/github/github-mcp-server/blob/c59e8c199efbf14467211861de44afaeeb6873e3/README.md) Checked 2026-10-14 https://github.com/github/github-mcp-server/blob/c59e8c199efbf14467211861de44afaeeb6873e3/README.md Supports: summary, upstreamDescription, install, configExample, access, limitations, bestFor, review
- [Licence at the reviewed revision ↗](https://github.com/github/github-mcp-server/blob/c59e8c199efbf14467211861de44afaeeb6873e3/LICENSE) Checked 2026-10-14 https://github.com/github/github-mcp-server/blob/c59e8c199efbf14467211861de44afaeeb6873e3/LICENSE Supports: license
- [Pinned implementation or package metadata: cmd/github-mcp-server/main.go ↗](https://github.com/github/github-mcp-server/blob/c59e8c199efbf14467211861de44afaeeb6873e3/cmd/github-mcp-server/main.go) Checked 2026-10-14 https://github.com/github/github-mcp-server/blob/c59e8c199efbf14467211861de44afaeeb6873e3/cmd/github-mcp-server/main.go Supports: review, install, language

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### GitKraken MCP Server ↗ GitKraken's official MCP server connects assistants to git history, branches, issues, pull requests and multi-repo workflows across GitHub, GitLab, Azure DevOps, Bitbucket and Jira. Ships inside the gk CLI (npm @gitkraken/gk), installs via GitLens, and is packaged for the Docker MCP Catalog.](/mcp-servers/gitkraken/)[### Git MCP reference server ↗ Inspect local Git history and diffs, then stage, commit, or switch branches through explicit tools.](/mcp-servers/git/)[### GitLab MCP ↗ Connect a client to project, repository, review and CI context on GitLab.com or an enabled GitLab instance.](/mcp-servers/gitlab/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
