google-gemini / google-gemini/gemini-cli
Support Oauth 2.1 DCR for MCP servers
- Dominant language
- TypeScript
- Stars
- 107k
- Forks
- 14.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 45
Description
### What would you like to be added?
Support Oauth 2.1 and DCR for MCP configurations. Such as Atlassian.
### Why is this needed?
Without supporting Oauth 2.1, newer mcp authentication mechanisms fail in gemini cli.
The error you receive in gemini cli is "No client ID provided and dynamic registration not supported"
### Additional context
Antigravity cli supports it but gemini cli does not. Which means mcp servers like Atlassian are not supported (currently using the legacy mcp url to get it to work but its deprecated)
https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-oauth-2-1/
https://benjamin-fuqua.medium.com/why-your-custom-oauth-tokens-fail-with-the-atlassian-mcp-server-and-how-dcr-fixes-it-2566b779f795
Contributor guide
Research direction
Start by reviewing the MCP authentication flow and the linked Atlassian OAuth 2.1 and DCR guidance. Define how OAuth 2.1 and dynamic client registration should work for MCP configurations, then verify that an MCP server requiring DCR no longer produces the reported missing-client-ID error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100