Oauth in STDIO server #2784
SamMorrowDrums
announced in
Announcements
Replies: 1 comment
-
|
Yes |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello from the GitHub MCP Server Maintainers 👋,
Shipping in v1.5.0: the local (stdio) server now supports OAuth 2.1 login, so you no longer need to create, store, and rotate a Personal Access Token. Log in through your browser on first use — the token is kept in memory only and is never written to disk.
📖 Full guide: Local Server OAuth Login
How it works
--oauth-client-id+--gh-host). Both OAuth Apps and GitHub Apps are fully supported.Headless or no browser?
There's a device-code fallback for SSH sessions, containers, and other headless environments — you'll get a code to enter on another device. If your client doesn't support URL elicitation, the server detects it, tells you, and falls back automatically.
Running in Docker
Docker needs a fixed callback port published to loopback so the container's login callback is reachable:
The native binary doesn't need this — it uses a random loopback port. Every install guide now leads with an OAuth config block in its client's own syntax.
Security
We want your feedback! 💬
Auth is sensitive and this is new, so we want to hear what breaks:
Drop a comment below — we're listening! 🙏
Beta Was this translation helpful? Give feedback.
All reactions