Support Oauth client secret in refresh

Open
#784 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
authentication

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.

Description

enhancement P2

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

Dominant language
Rust
Stars
3.9k
Forks
645
Avg merge
4d 13h
Merged PRs (30d)
36

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/rust-sdk

All issues in modelcontextprotocol/rust-sdk

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.