How to use GitHub with Cursor
You want GitHub inside Cursor so it can review pull requests and assign follow-up work, triage repository issues, prepare a pull request from a code change, and audit repository access and activity — without you copy-pasting between tabs. Here is the whole setup, once.
Create your GitHub gateway
The gateway is the thing Cursor connects to, and it is where you decide which GitHub tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your GitHub tools
In the dashboard, create a gateway and pick the GitHub tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Cursor
Cursor does not refresh MCP OAuth tokens automatically. For a persistent connection, set Authorization to “Arcade Headers” on the gateway in the dashboard.
-
Open MCP settings
Command Palette (⌘⇧P / Ctrl+Shift+P) → Open MCP Settings, then click “New MCP Server”.
-
Add the gateway to mcpServers
{ "mcpServers": { "mcp-arcade": { "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>" } } } -
Try it out
Ask Cursor to use one of your GitHub tools.
Full Cursor guide in the docs steps verified 2026-08-13
Try these GitHub prompts
Cursor can now act on your GitHub account. Click a prompt to copy it.
Control repository access and require approval before an agent creates files, merges pull requests, or changes labels with Contextual Access policies.