Claude Code 2.1.292 switches stdio MCP servers to a new protocol, docs still say opt-in

Claude Code 2.1.292 switches stdio MCP servers to a new protocol, docs still say opt-in

Claude Code 2.1.292 changes how it connects to local MCP servers, and the documentation that explains the setting still describes the older behaviour. The release notes list "Changed local (stdio) MCP server connections to negotiate protocol version 2026-07-28 by default on every install, including Bedrock, Vertex and Foundry; MCP_PROTOCOL_NEGOTIATION=legacy opts out".

Claude Code terminal running quality control on single-cell RNA sequencing data

A terminal window with a Claude Code session running inside it. Image: Anthropic

The build reached npm at 17:10 UTC on October 6, by the registry's own timestamp, read at 22:58 UTC the same day. Read 24 minutes earlier, at 22:53 UTC, Claude Code's MCP documentation still had it asking stdio servers "on Claude Code v2.1.285 or later ... as Anthropic rolls that change out", and told readers to set MCP_PROTOCOL_NEGOTIATION to auto "to have it ask connector and stdio servers in every session".

The environment variable reference points back at the unchanged page

The environment variable reference, read at 22:53 UTC on October 6, defines MCP_PROTOCOL_NEGOTIATION as controlling "whether Claude Code probes servers for MCP protocol revision 2026-07-28", with auto to "probe HTTP, claude.ai connector, and stdio servers" and legacy to "probe none". With the variable unset, it says, "Claude Code probes the servers described under MCP client runtimes", which is the page carrying the rollout wording.

The same reference lists probing stdio servers among the things Claude Code does only in sessions where it fetches feature flags, "unless you set MCP_PROTOCOL_NEGOTIATION=auto". The release note attaches no flag fetch and no condition, and says every install.

A channel server on the new revision is not registered

Anthropic's documentation spells out one consequence of the newer handshake: "a channel server that negotiates MCP protocol revision 2026-07-28 can't deliver channel messages, so Claude Code doesn't register it as a channel". A server that does not support the revision "connects on the earlier handshake and registers as before".

The documented route back is the same variable. Setting it to legacy "keeps every server on" the earlier handshake, which is all of them rather than the one with the problem. Anthropic has published no report of a channel server failing this way, and the line is filed as a change rather than a fix.

All of this runs on the v2 MCP client runtime

Both documents scope the behaviour to Claude Code's v2 MCP client runtime, built on MCP TypeScript SDK 2.0, "which adds MCP protocol revision 2026-07-28". The variable itself needs "Claude Code v2.1.221 or later", while the rollout wording still names Claude Code 2.1.285 as the floor for stdio probing.

The newer revision brings servers something as well as taking channels away. On connections that use it, the documentation says, Claude Code "declares elicitation: {form: {}, url: {}} in its client capabilities, so a server there can request either mode through the protocol's standard elicitation request". Anthropic can also hold a named server on the earlier protocol with a feature flag Claude Code fetches.

2.1.292 carries two more MCP entries. One leaves out an MCP tool whose name runs past 128 characters, where before "every request" failed, and names that tool in an error. The other stops claude -p and SDK sessions waiting for HTTP and SSE servers to answer resources/list on the first turn.

A third entry softens the new handshake for servers that ignore it: local servers that do not answer the protocol check are remembered for seven days after one slow connect, then connected the older way without the wait. Anthropic has shipped three Claude Code builds since 2.1.289 on October 3, at close to one a day.

Leave a Comment

Your email address will not be published. Required fields are marked *