Easily connect to the GitHub MCP Server using the hosted version – no local setup or runtime required.
URL: https://api.githubcopilot.com/mcp/
The remote GitHub MCP server is built using this repository as a library, and binding it into GitHub server infrastructure with an internal repository. You can open issues and propose changes in this repository, and we regularly update the remote server to include the latest version of this code.
The remote server has additional tools that are not available in the local MCP server, such as the create_pull_request_with_copilot tool for invoking Copilot coding agent.
Below is a table of available toolsets for the remote GitHub MCP Server. Each toolset is provided as a distinct URL so you can mix and match to create the perfect combination of tools for your use-case. Add /readonly to the end of any URL to restrict the tools in the toolset to only those that enable read access. We also provide the option to use headers instead.
These toolsets are only available in the remote GitHub MCP Server and are not included in the local MCP server.
| Name | Description | API URL | 1-Click Install (VS Code) | Read-only Link | 1-Click Read-only Install (VS Code) |
|---|---|---|---|---|---|
| Copilot coding agent | Perform task with GitHub Copilot coding agent | https://api.githubcopilot.com/mcp/x/copilot | Install | read-only | Install read-only |
The Remote GitHub MCP server has optional headers equivalent to the Local server env vars:
X-MCP-Toolsets: Comma-separated list of toolsets to enable. E.g. "repos,issues".- Equivalent to
GITHUB_TOOLSETSenv var for Local server. - If the list is empty, default toolsets will be used. If a bad toolset is provided, the server will fail to start and emit a 400 bad request status. Whitespace is ignored.
- Equivalent to
X-MCP-Readonly: Enables only "read" tools.- Equivalent to
GITHUB_READ_ONLYenv var for Local server. - If this header is empty, "false", "f", "no", "n", "0", or "off" (ignoring whitespace and case), it will be interpreted as false. All other values are interpreted as true.
- Equivalent to
Example:
{
"type": "http",
"url": "https://api.githubcopilot.com/mcp/",
"headers": {
"X-MCP-Toolsets": "repos,issues",
"X-MCP-Readonly": "true"
}
}The Remote GitHub MCP server also supports the URL path parameters:
/x/{toolset}/x/{toolset}/readonly/readonly
Note: {toolset} can only been a single toolset, not a comma-separated list. To combine multiple toolsets, use the X-MCP-Toolsets header instead.
Example:
{
"type": "http",
"url": "https://api.githubcopilot.com/mcp/x/issues/readonly"
}