Repository navigation
OAuth: client_credentials configuration results in authorization_code flow #7306
Closed as not planned
Description
Description
Hi Team,
According to you docs we should be able to connect MCP's using pre-registered clients -
https://opencode.ai/docs/mcp-servers/#pre-registered
I have applied the following configuration
"saas-context": {
"type": "remote",
"url": "https://sass/mcp/context",
"enabled": true,
"oauth": {
"clientId": "CLIENT_ID",
"clientSecret": "CLIENT_SECRET",
"scope": "jobs:read"
}
}
The requests appear to be going here -
Path Excluded: /public/public-api/mcp/context
Path Excluded: /.well-known/oauth-protected-resource/api/mcp/context
Path Excluded: /.well-known/oauth-protected-resource
Path Excluded: /.well-known/oauth-authorization-server/api/mcp/context
Path Excluded: /.well-known/oauth-authorization-server
Path Excluded: /oauth2/authorize
This opens a browser to do a authorization_code flow but it should do client_credential flow because clientId and clientSecret is provided.
Regards,
Tarek
Plugins
No response
OpenCode version
1.1.6
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
macOS 26
Terminal
vscode
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Jan 8, 2026
This issue might be related to existing OAuth/MCP authentication issues. Please check:
The core issue here is that when
clientIdandclientSecretare provided, the client_credentials OAuth flow should be used instead of the authorization_code flow. These related issues may contain useful context about MCP OAuth handling.Feel free to ignore if your specific case differs from these issues.
thdxr commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.