GitHub MCP server

GitHub × Cursor

Use the GitHub MCP server
in Cursor

Repos, issues, and pull requests from your GitHub account — in your AI. This guide connects GitHub to Cursor (the AI code editor) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · Connects with your API key

Setup: GitHub in Cursor

Cursor adds MCP servers via MCP settings or install deep links. The gateway route takes about two minutes:

  1. Connect GitHub to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to Cursor' — Cursor opens and asks to install the gateway.
  3. Confirm and approve the sign-in.
  4. GitHub's tools are now available to Cursor's agent, governed by your rules.

What to ask once it’s connected

Summarize the open PRs waiting for my review.
What changed on main since Friday?
Create an issue from this bug description.
Which issues are labeled critical and unassigned?

Why route it through a gateway

One URL, every client

The same GitHub connection works in Claude, Claude Code, ChatGPT, VS Code too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool GitHub exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything Cursor did with GitHub — searchable, exportable, auditable.

Scanned and probed

GitHub passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: GitHub in Claude · GitHub in Claude Code · GitHub in ChatGPT · GitHub in VS Code