G

GitHub MCP Server

MCP detected 2026-11-17

Details
Endpoint
https://api.githubcopilot.com/mcp/
Transport
sse
Docs
https://docs.github.com/en/copilot/how-tos/copilot-in-your-ide/customize-copilot/extend-copilot-with-tools-and-context/set-up-the-github-mcp-server
Authentication
GitHub MCP remote-server OAuth authorization oauth2 discovered
OAuth · resolves from well-known metadata

For the remote GitHub MCP server at https://api.githubcopilot.com/mcp/, compatible MCP hosts can use one-click OAuth sign-in. GitHub's MCP docs say you do not need to create a PAT for this path: configure the server URL in your MCP host or IDE and approve access in the browser when prompted. See Setting up the GitHub MCP Server and the GitHub MCP Server README.

GitHub personal access token (classic or fine-grained) bearer discovered Get token ↗
Authorization: Bearer <credential>

Create a personal access token from your GitHub account settings using Managing your personal access tokens. Choose scopes or fine-grained permissions based on the API or MCP actions you need. GitHub's docs note that fine-grained PATs include read access to public repositories, while classic PATs need scopes such as public_repo for public-repo access.