MCP Gateway · Claude Cowork
Connect GitHub to Claude Cowork
Engineering managers hand Cowork the GitHub chores that take an afternoon: weekly reports, backlog cleanups, cross-repository audits. Once the organization's marketplace syncs GitHub into Claude, a long Cowork session can read and update issues and pull requests as it goes. Speakeasy decides whether to allow each prompt before that step runs, and OTLP telemetry from Cowork records who started the session.
- Category
- Developer tools
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the GitHub server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
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.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use GitHub from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with GitHub
Write the weekly engineering report
Cowork reviews the week's merged pull requests and closed issues across the team's repositories and writes a report of what shipped, what slipped and what's next.
Clean up a stale issue backlog
Hand Cowork a repository with hundreds of old issues. It reads each one, labels duplicates and stale reports, and leaves a comment before closing the ones that no longer apply.
Audit repositories for missing workflows
Ask Cowork to go through the organization's repositories and list which ones lack a CI workflow, then write up the gaps for the platform team.
Control
What Speakeasy can see and stop in Claude Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Do members need GitHub access to get the plugin in Cowork?
Is GitHub Enterprise Server covered by the setup?
How do Claude Cowork users get GitHub?
Are GitHub calls from Claude Cowork logged?
Connect more