GitHub MCP server

A GitHub MCP server exposes GitHub to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call its tools to work with GitHub. The server in this catalog is the official GitHub MCP server.

Agents can manage repos, issues, pull requests, and workflows. The registry has not published an individual tool list for this server yet, so no tools are shown on this page.

Connecting the GitHub MCP server directly to each client means a separate credential per developer, no inventory of who can reach GitHub through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the GitHub server, so sign-in runs through your identity provider, role-based access decides which teams can call which GitHub tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to GitHub and to every other server in your catalog.

Add the GitHub server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which GitHub tools. Every prompt, response, and tool call is inspected and logged at the gateway.

Community-built GitHub MCP servers wrap the same GitHub surface but are not vendor-maintained. This catalog lists the official GitHub MCP server. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access controls, and an audit trail of every call, whichever credential the server itself uses.