feat(mcp): resolve and negotiate the dual-era protocol selection - #4086
Merged
ignaciojimenezr merged 1 commit intoAug 18, 2026
Merged
Conversation
Act on the `auto` selection published as client data: resolve it to "no pin" at connect time, keep it out of the connection profile's wire pin, and let the client manager negotiate the era instead of advertising one. The protocol dropdown gains the matching Automatic option. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
This was referenced Aug 18, 2026
Contributor
Internal previewPreview URL: https://mcp-inspector-pr-4086.up.railway.app |
ignaciojimenezr
temporarily deployed
to
preview-pr-4085
August 18, 2026 18:57 — with
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #4085 — merge that first. Replaces #3828, which mixed data and behavior; this is the behavior half.
autoprotocol setting that feat(host-catalog): ChatGPT dual-era protocol — client data and negotiation #4085 publishes.automeans "don't pin a version" — the client negotiates the era with the server instead of announcing one up front.🤖 Generated with Claude Code
Summary by cubic
Implements automatic MCP protocol negotiation across the 2025/2026 eras and treats "auto" as a stored selection policy. Automatic now negotiates the era on connect (no wire pin) and respects the client’s advertised support list, which can change reconnect behavior.
"auto". At connect time the SDK reduces"auto"to no pin and negotiates via discovery; explicit server pins still win. The connection profile never emits"auto"on the wire.supportedProtocolVersionsin Automatic mode (per-server or manager default). It negotiates only within that list and rejects servers that counter-offer an unlisted version. Explicit pins remain strict."auto"; legacy rows with no pin render as Automatic without rewriting. The dropdown only offers advertised versions and warns on any unadvertised pin.Review and rollout
mcpProfile.mcpProtocolVersioncan be"auto"in stored configs and Host JSON; connection profiles still carryundefinedfor the wire pin.supportedProtocolVersions(per server or manager default), include all eras you want to negotiate; Automatic will fail when the server selects a version outside that list. No data migration is required.Written for commit 008b419. Summary will update on new commits.