modelcontextprotocol / modelcontextprotocol/rust-sdk
Support Oauth client secret in refresh
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.9k
- Forks
- 645
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 36
Description
Is your feature request related to a problem? Please describe.
I'm trying to connect to an MCP server that uses DCR and returns an Oauth client ID and client secret. The auth works fine, but oauth refresh fails due to missing client_secret. Error: invalid_client
Describe the solution you'd like
Support storing and then using client secret in refresh.
Describe alternatives you've considered
Setting up Oauth myself.
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the OAuth dynamic client registration and token-refresh entry points in the Rust SDK, then trace how the client ID is stored and reused. Add coverage for a DCR response containing a client secret and verify that refresh succeeds without an invalid_client error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100