You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Features
client_credentials grant for OAuth MCP servers (#619) — MCP server registrations of type oauth now accept a grantType, defaulting to authorization_code so every existing server is unaffected. Choosing client_credentials swaps the browser-based authorization flow for a single machine-to-machine token request: no proxy callback, no consent window, no PKCE. This unblocks authorization servers (e.g. some Auth0 tenants) that refuse loopback redirect URIs outright, where the interactive flow was previously impossible to complete.
Requires clientId and clientSecret together, and rejects redirectUri since it no longer applies.
Adds a configurable audience field (Auth0's spelling of "which API is this token for"; RFC 8707 resource is sent alongside it for standards-compliant providers).
No refresh token is stored for this grant — renewal re-mints from the keychain on each use, per RFC 6749 §4.4.3. The status row reads "Connected · renews in …", and a failed renewal reads "Needs new credentials".
Registration from a scheduled (unattended) thread is still refused for both grant types, since a client_credentials server has no consent screen to put a human in front of the connection.
Bug Fixes
audience now actually applies to the authorization_code grant — previously accepted and persisted in settings but silently never sent on the authorization request, so it had no effect for interactive OAuth servers that need an API-scoped token (e.g. Auth0). Now wired into the authorization URL alongside the existing resource parameter.
Notes
Secret custody is unchanged from the original OAuth MCP support (v0.45.0 / #585): client secrets live only in the OS keychain, never in data.json or a tool-call transcript.
No migration needed — existing authorization_code registrations are untouched by this release.