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
Support explicit OAuth credentials for remote MCP servers
Add support for configuring explicit OAuth client credentials (clientId,
clientSecret, callbackPort, scopes) on remote MCP server toolsets. This
fixes connections to MCP servers that do not support Dynamic Client
Registration (RFC 7591), such as Slack and GitHub.
Key changes:
- Add RemoteOAuthConfig to config types with clientId, clientSecret,
callbackPort, and scopes fields
- Stop fabricating registration_endpoint when the server doesn't
advertise one in metadata discovery
- Use explicit credentials in the managed OAuth flow when configured,
falling back to dynamic registration when available
- Support fixed callback port for OAuth redirect URI
- Add scopes parameter to BuildAuthorizationURL
- Validate callbackPort range (1-65535) and oauth on non-mcp types
- Update agent-schema.json with RemoteOAuthConfig definition
- Add example config (examples/remote_mcp_oauth.yaml)
Fixes#2248
Co-Authored-By: nicholasgasior <nicholasgasior@users.noreply.github.com>
Co-Authored-By: rumpl <rumpl@users.noreply.github.com>
Assisted-By: docker-agent
0 commit comments