Connect GitHub to Cursor
Give Cursor governed access to GitHub’s 100 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add GitHub to Cursor in four steps
Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.
- 1
Approve GitHub in Runlayer
Add GitHub from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Cursor to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, GitHub’s 100 tools show up in Cursor’s own tool list.
Cursor setup guide - 3
Sign in to GitHub
Each user signs in to GitHub with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use GitHub from Cursor
GitHub’s approved tools appear in Cursor. Every call is checked against policy and recorded.
Tools
100 GitHub tools in Cursor
Runlayer policy decides which of these Cursor users can call.
Get actions
Get details about specific GitHub Actions resources.
List actions
Tools for listing GitHub Actions resources.
Actions run trigger
Trigger GitHub Actions workflow operations, including running, re-running, cancelling workflow runs, and deleting workflow run logs.
Add comment to pending review
Add review comment to the requester's latest pending pull request review.
Add issue comment
Add a comment and/or reaction to a specific issue or issue comment in a GitHub repository.
Add reply to pull request comment
Add a reply and/or reaction to an existing pull request comment.
Assign copilot to issue
Assign Copilot to a specific issue in a GitHub repository.
Assign copilot to issue with intent
Assign Copilot to a specific issue in a GitHub repository.
Control
What Runlayer can see and stop in Cursor
Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.
Gateway policy (available)
Every GitHub call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.
Block output after it runs (available)
Runlayer can block a tool’s output before Cursor’s model sees it.
Redact output in place (not available)
Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Cursor
- Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
- The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.
Frequently asked questions
Connect more