Connector plugin · listing tai42/connector-githubInstall
Permissions
Provides
github
Connector — OAuth connector for GitHub over GitHub’s hosted MCP server.
Registers the github connector: one OAuth connection per alias against GitHub’s
hosted MCP server at https://api.githubcopilot.com/mcp/. The plugin is pure
descriptor data and ships no package; each sub-service selects one GitHub MCP
toolset through the X-MCP-Toolsets header. The runtime’s connector engine
runs the OAuth flow, seals the tokens, and reaches the MCP server over HTTP.
Install
Install the descriptor into the running server with the CLI:connectors: entry (each sub-service is
one toolset):
manifest.yml
Register a GitHub App
Register a GitHub App (not a plain OAuth App) and turn ON “Expire user authorization tokens”. With expiry enabled the token response carries arefresh_token and expires_in, which the platform requires on Connect. A plain
OAuth App issues no refresh token and will fail Connect loudly.
- authorize:
https://github.com/login/oauth/authorize - token:
https://github.com/login/oauth/access_token
scope query param is ignored). Grant the permissions the toolsets you enable
need — Contents and Metadata (repos), Issues, Pull requests, Actions, Discussions,
Code scanning alerts, Secret scanning alerts, Dependabot alerts, and the
organization/member read permissions.
Add this exact callback URL, where {origin} is your deployment’s public origin
(or CONNECTORS_OAUTH_BRIDGE_URL when you run a shared bridge):
CONNECTORS_* settings — the key-encryption key
(CONNECTORS_KEK), the state HMAC key (CONNECTORS_STATE_HMAC_KEY), and the
redirect-URI allowlist (or CONNECTORS_OAUTH_BRIDGE_URL) — are shared by every
connector and are described in Connectors. The origin you
registered with GitHub must appear in the redirect-URI allowlist, and it must be
https for anything but a local host.
Toolsets and scopes
Each sub-service is one GitHub MCP toolset, selected by theX-MCP-Toolsets
header. The scope list names the OAuth-App scope each toolset needs; for a GitHub
App map each to the equivalent App permission.
See also
- Connectors — the model, the token lifecycle, and the shared engine settings.
- Connect an OAuth provider — the end-to-end walkthrough.

