Summary
Full OAuth 2.1 login support for the stdio server. Replaces the mandatory PAT with a lazy, auto-refreshing OAuth flow triggered on first tool call. Three coordinated pieces of work:
Upstream reference
Fork conflict
None. OAuth is an authentication layer entirely separate from the fork's project-management and issue-graph tooling.
Context
The stdio GitHub MCP server previously required users to provision a GitHub personal access token. OAuth 2.1 PKCE login eliminates this friction: official binaries on github.com ship with baked-in credentials, so users just run the server and complete a browser login on first use. GHES and custom-app users bring their own --oauth-client-id.
Summary
Full OAuth 2.1 login support for the stdio server. Replaces the mandatory PAT with a lazy, auto-refreshing OAuth flow triggered on first tool call. Three coordinated pieces of work:
internal/oauth): PKCE + device-code flows, Manager, Prompter interfaceBearerAuthTransport,RunStdioServermiddleware,--oauth-*flagsinternal/buildinfo,docs/oauth-login.md, README/server.json updatesUpstream reference
Fork conflict
None. OAuth is an authentication layer entirely separate from the fork's project-management and issue-graph tooling.
Context
The stdio GitHub MCP server previously required users to provision a GitHub personal access token. OAuth 2.1 PKCE login eliminates this friction: official binaries on github.com ship with baked-in credentials, so users just run the server and complete a browser login on first use. GHES and custom-app users bring their own
--oauth-client-id.