Skip to main content
Back to the GitHub MCP server

MCP Gateway · Cursor

GitHub icon

Connect GitHub to Cursor

Reviewing and shipping code means jumping between Cursor and GitHub. With the GitHub MCP server behind the Speakeasy gateway, Cursor's chat can read and act on issues and pull requests while the files are open beside it. Cursor hooks send each prompt and tool call to Speakeasy and fail closed, and every hook event carries the user's email.

Category
Developer tools
Cursor
Editor and terminal

Behind the MCP Gateway

Run GitHub MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every GitHub call inspected and logged.

Deploy on MCP Gateway

Before you start

What GitHub needs first

A GitHub organization administrator; an organization owner if the org restricts OAuth apps does the GitHub side of the setup.

  • You need admin access to the GitHub organization that will own the OAuth app.
  • The guide covers standard GitHub.com only, not Enterprise Cloud with data residency or Enterprise Server.
  • Orgs that restrict OAuth apps need an owner to approve the app.

In GitHub

  1. Open the organization's Developer settings > OAuth apps.
  2. Register an OAuth app with the Speakeasy callback URL.
  3. Copy the Client ID and generate a client secret.
  4. If the org restricts OAuth apps, have an owner approve the access request.
Full GitHub setup guide in the docs

Set up

Add GitHub to Cursor in 4 steps

  1. 01

    Add GitHub from the catalog

    An admin finds GitHub in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use GitHub

    Give teams the mcp:connect scope on the GitHub server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds GitHub to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use GitHub from Cursor

    The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    From then on, GitHub's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with GitHub

Review a teammate's pull request

Ask Cursor to pull up a teammate's pull request and walk through it next to the code you have open, then leave review comments from the chat.

Link an issue while you code

When a fix in the editor resolves a reported problem, Cursor finds the matching GitHub issue and references it in the pull request so it closes on merge.

Triage new issues for your area

Ask Cursor for the recently opened issues in your repository, label the ones that belong to your team and assign them before standup.

Control

What Speakeasy can see and stop in Cursor

The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.

Tool logs

Gateway

Every GitHub call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the GitHub tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to GitHub can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

Do GitHub tools run in Cursor Cloud agents?
Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
Can GitHub use in Cursor count against a budget?
Yes. Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
How do Cursor users get GitHub?
An admin adds GitHub from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the GitHub tools their access allows.
Are GitHub calls from Cursor logged?
Yes. GitHub calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

GitHub in other clients

AI everywhere.

Control here.