Connect GitHub MCP (remote) to Cursor
GitHub's hosted MCP server. Agents read code, issues and pull requests and open PRs with nothing to run on your machine, connecting with a personal access token.
MCP serverOfficialChecked 2026-11-16
Before you start
- Cursor installed (see its MCP documentation (opens in a new tab)).
- GitHub MCP (remote) is available on macOS, Windows, Linux and the web.
- Create a fine-grained personal access token with only the repositories and permissions you need, and set it as
GITHUB_PERSONAL_ACCESS_TOKENin your environment. For read-only tools, end the URL with/readonly. GitHub Enterprise Server doesn't support the hosted server.
Step 1: Add GitHub MCP (remote) to Cursor
Or add it to the project
Add this to
.cursor/mcp.json, or to~/.cursor/mcp.jsonto use it in every project..cursor/mcp.json { "mcpServers": { "github-remote": { "url": "https://api.githubcopilot.com/mcp/", "headers": { "Authorization": "Bearer ${env:GITHUB_PERSONAL_ACCESS_TOKEN}" } } } }Good to know- Cursor reads
GITHUB_PERSONAL_ACCESS_TOKENwhen it starts. Set the variable, then open Cursor from that terminal so it can see it.
- Cursor reads
Step 2: Check it's connected
Open Cursor Settings, find the MCP section and check the server is enabled with its tools listed.
Step 3: Try a first request
Ask Cursor something that only works with GitHub MCP (remote) connected:
Say to Cursor List the open issues in this repository that mention design and group them by label.
If it doesn't work
- Project servers live in
.cursor/mcp.json; servers for every project live in~/.cursor/mcp.json. - After editing the file by hand, toggle the server off and on in settings, or restart Cursor.
- The Output panel (MCP Logs) shows why a server failed to start.





