--- 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 ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-21 Evidence 4 linked sources Publisher GitHub Licence MIT ↗ Revision 85598ba6e125 Read what was—and wasn’t—checked ↓ “The GitHub MCP Server connects AI tools directly to GitHub's platform.” GitHub · upstream description ↗ 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. ### A good fit for - Investigating a failing GitHub Actions run alongside the related pull request. - Reading repository context and preparing issue or pull-request updates. ### 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. 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: remote configuration, toolsets, permissions and read-only/lockdown modes. - go.mod and cmd/github-mcp-server/main.go: runtime, stdio/HTTP entrypoints and authentication/read-only flags. - LICENSE: MIT terms for repository source. ### Our findings - The executable has separate stdio and HTTP commands and carries the read-only setting into each server configuration. - The command entrypoint rejects conflicting PAT, GitHub App and OAuth authentication configuration. - Tool availability and credential authority are separate: exposing a tool does not itself grant the account permission to perform it. ### Not established by this review - Server startup, authentication and tool execution were not tested. 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 ↗ - 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. - GitHub setup and tool reference ↗ Checked 2026-09-21 https://github.com/github/github-mcp-server/blob/85598ba6e1256f7ebf4867b95d63b833c4549264/README.md Supports: summary, install, compatibility, access, transports, configExample, whySelected, bestFor, limitations - GitHub server entrypoints ↗ Checked 2026-09-21 https://github.com/github/github-mcp-server/blob/85598ba6e1256f7ebf4867b95d63b833c4549264/cmd/github-mcp-server/main.go Supports: review, transports, access - Go module manifest ↗ Checked 2026-09-21 https://github.com/github/github-mcp-server/blob/85598ba6e1256f7ebf4867b95d63b833c4549264/go.mod Supports: language, review - Repository licence ↗ Checked 2026-09-21 https://github.com/github/github-mcp-server/blob/85598ba6e1256f7ebf4867b95d63b833c4549264/LICENSE Supports: license KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### 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/)[### Asana MCP V2 ↗ Asana’s current workspace-scoped MCP connection for task, project and portfolio workflows.](/mcp-servers/asana/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)