Skip to main content
Back to the GitHub MCP server

MCP Gateway · ChatGPT

GitHub icon

Connect GitHub to ChatGPT

Support, success and program managers can ask ChatGPT about engineering work tracked on GitHub without learning the GitHub interface. A workspace admin imports the plugin marketplace and sets per role whether the plugin is installed or available. At the gateway, every GitHub tool call is checked for prompt injection, has PII redacted, and is tied to a named employee.

Category
Developer tools
ChatGPT
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 ChatGPT 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. ChatGPT connects to the GitHub server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect ChatGPT

    Import the organization's plugin marketplace into the ChatGPT workspace and set who gets each plugin.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Give the importing workspace admin collaborator access to the marketplace repository, and connect their GitHub account in ChatGPT under Plugins > GitHub > Manage.

    In ChatGPT, open Admin > Plugins > Add > Import marketplace.

    Set each plugin's installation policy, Installed or Available, per role.

    Enable the MCP servers the plugin connects to.

  4. 04

    Sign in and use GitHub from ChatGPT

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

The marketplace syncs from GitHub once a day. Use Sync now to pick up a change straight away.

Use cases

What ChatGPT users do with GitHub

Answer a customer about a known bug

When a customer asks whether a problem is being fixed, ChatGPT finds the matching GitHub issue and tells the support rep its status and latest discussion.

Turn a feature request into an issue

After a customer call, ask ChatGPT to file a GitHub issue that captures the request in the customer's words, so engineering sees it where they work.

Prepare a launch checklist

Program managers ask ChatGPT which pull requests and issues are still open for a launch, then turn the list into a checklist for the go or no-go meeting.

Control

What Speakeasy can see and stop in ChatGPT

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

Conversation import

ChatGPT

ChatGPT activity can be imported through OpenAI's Compliance API for review after the fact. It can't block in real time.

  • The workspace import needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Can ChatGPT stop a GitHub action in real time?
No. ChatGPT activity can be imported through OpenAI's Compliance API for review after the fact, but it can't block in real time. Which GitHub tools a role can call is decided at the gateway.
Which ChatGPT plans can add GitHub through Speakeasy?
The workspace import needs a ChatGPT Business, Enterprise or Edu admin. The marketplace then syncs from GitHub once a day, and Sync now picks up a change straight away.
How do ChatGPT users get GitHub?
An admin adds GitHub from the Speakeasy MCP Catalog and grants access by team or role. Import the organization's plugin marketplace into the ChatGPT workspace and set who gets each plugin. Each person then sees only the GitHub tools their access allows.
Are GitHub calls from ChatGPT 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.