MCP Gateway · Claude Code
Connect GitHub to Claude Code
Most of what Claude Code writes ends up on GitHub. With the official GitHub MCP server behind the Speakeasy gateway, Claude Code can work with repositories, issues and pull requests in the same terminal session as the code. Agent hooks send each tool call to Speakeasy before Claude Code runs it, so an action a team shouldn't take can be denied.
- Category
- Developer tools
- Claude Code
- CLI
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.
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
- Open the organization's Developer settings > OAuth apps.
- Register an OAuth app with the Speakeasy callback URL.
- Copy the Client ID and generate a client secret.
- If the org restricts OAuth apps, have an owner approve the access request.
Set up
Add GitHub to Claude Code in 4 steps
- 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.
- 02
Choose who can use GitHub
Give teams the
mcp:connectscope 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. - 03
Connect Claude Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use GitHub from Claude Code
The first time Claude Code 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 Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with GitHub
Open a pull request from your branch
When the change is ready, Claude Code opens the pull request on GitHub with a description of what changed and why, without a trip to the browser.
File an issue for a bug you found
If Claude Code spots a defect outside the current change, it files a GitHub issue in the right repository with the file and the failing case, then carries on.
Edit a workflow alongside its repo
While you change a CI workflow file, Claude Code can manage the repository's GitHub workflows from the same session, keeping the edit and its GitHub state together.
Control
What Speakeasy can see and stop in Claude Code
The gateway covers every client the same way. The rest depends on what Claude Code 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 Claude Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Can Claude Code be limited to read-only GitHub actions?
Does the GitHub setup cover GitHub Enterprise Server?
How do Claude Code users get GitHub?
Are GitHub calls from Claude Code logged?
Connect more