Skip to content

[MCP] Don't require experimental_use_rmcp_client for no-auth http servers #4689

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Oct 3, 2025
Merged

[MCP] Don't require experimental_use_rmcp_client for no-auth http servers #4689

merged 1 commit into from
Oct 3, 2025
+0 −14

Conversation

gpeal
Copy link
Collaborator

@gpeal gpeal commented Oct 3, 2025

The experimental_use_rmcp_client flag is still useful to:

  1. Toggle between stdio clients
  2. Enable oauth beacuse we want to land Allow clients to override client_name modelcontextprotocol/rust-sdk#469, Fix oauth .well-known metadata discovery #4677, and binary signing before we enable it by default

However, for no-auth http servers, there is only one option so we don't need the flag and it seems to be working pretty well.

@gpeal gpeal requested a review from bolinfest October 3, 2025 20:54
@gpeal gpeal enabled auto-merge (squash) October 3, 2025 21:15
@gpeal gpeal merged commit d13ee79 into main Oct 3, 2025
20 checks passed
@gpeal gpeal deleted the gpeal/remove-flag-for-streaming branch October 3, 2025 21:15
@github-actions github-actions bot locked and limited conversation to collaborators Oct 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@bolinfest bolinfest bolinfest approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@gpeal @bolinfest