Skip to main content
Back to the GitHub MCP server

MCP Gateway · Claude

GitHub icon

Connect GitHub to Claude

Product managers, support leads and engineering managers often need GitHub answers without the GitHub interface. In Claude, they can ask what's open, what merged and what's blocked, and get a written answer. An Owner adds the gateway as a custom connector once, each person connects from Customize > Connectors, and people only see the servers their role can reach.

Category
Developer tools
Claude
Web, desktop and mobile

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 Claude 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 Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use GitHub from Claude

    The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with GitHub

Summarize open issues for a feature

Ask Claude for the open GitHub issues on a feature area and get a plain-language summary of what users reported and what's still unresolved.

Draft release notes from merged work

Claude reads the pull requests merged since the last release and drafts customer-facing release notes grouped into fixes and new features.

Check status before a stakeholder update

Before a weekly update, ask Claude which pull requests for a project are open, merged or waiting on review, and turn that into a short status note.

Control

What Speakeasy can see and stop in Claude

The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can non-engineers in Claude change GitHub repositories?
Only if their role allows it. The gateway decides which GitHub tools each team can call, so a product or support role can read issues and pull requests without write access.
Can Claude Enterprise block a prompt before it reaches GitHub?
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
How do Claude users get GitHub?
An admin adds GitHub from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the GitHub tools their access allows.
Are GitHub calls from Claude 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.