Github MCP Server

What github/github-mcp-server MCP server does

The github/github-mcp-server MCP server gives MCP clients access to GitHub context and operations. The README describes workflows such as browsing repositories, querying code, searching files, examining commits, managing issues and pull requests, monitoring GitHub Actions, analyzing build failures, reviewing security findings, and inspecting Dependabot alerts. It also mentions discussions, notifications, team activity, releases, and project-board workflows.

The supplied tool list contains two file-content tools: get_file_contents and getFileContents. The broader capabilities described in the README may depend on the selected toolsets and server configuration, so developers should verify the active tools in their MCP host.

How it works

GitHub hosts a remote instance at https://api.githubcopilot.com/mcp/. An MCP host connects to that HTTP endpoint and authenticates either through OAuth or a GitHub personal access token. The README identifies VS Code 1.101 or later as the requirement for remote MCP and OAuth support in VS Code, and lists Claude Desktop, Cursor, and Windsurf among compatible hosts.

A local deployment is also available for hosts that cannot connect to remote MCP servers. The documented Docker configuration publishes port 8085 on loopback and passes GITHUB_OAUTH_CALLBACK_PORT to the container. GitHub Enterprise Cloud with data residency uses an enterprise-specific remote endpoint, while GitHub Enterprise Server does not support remote hosting and should use the local configuration.

Setup and configuration

For remote use, add the GitHub HTTP endpoint to the host configuration. OAuth configuration can use the endpoint without an authorization header; PAT configuration adds an Authorization: Bearer header. The host must support remote MCP servers, and applicable GitHub policies must be enabled.

The github/github-mcp-server MCP server supports toolset configuration, including selecting toolsets beyond the defaults. Its documentation also describes an insiders mode, enabled either with /mcp/insiders in the URL or with the X-MCP-Insiders: true header. This mode is intended for early access to experimental tools.

For local use, run the published container image ghcr.io/github/github-mcp-server with interactive input, port mapping, and the OAuth callback-port setting. Authentication and host-specific setup still need to follow the project’s installation guidance.

Tools and capabilities

The documented scope covers:

• Reading repository contents and code files
• Searching files and examining commits
• Creating, updating, and managing issues and pull requests
• Reviewing code changes and triaging bugs
• Monitoring Actions runs and investigating build failures
• Managing releases and examining security or Dependabot findings
• Accessing discussions, notifications, and team activity

The listing specifically exposes get_file_contents and getFileContents, so availability of the other README-described operations should be confirmed after connection and toolset selection.

Limitations and notes

Remote access depends on MCP host support and host-specific OAuth or GitHub App configuration. PAT authentication is supported by hosts that support remote MCP servers, but configuration details vary by client. GitHub Enterprise Server cannot host the remote service. The insiders endpoint exposes early or experimental functionality, so it should be treated separately from the default toolset.