Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.292 ·

Local MCP servers now use protocol negotiation by default

Stdio MCP servers now use automatic protocol negotiation unless a server-side setting explicitly turns it off

You'll notice Improvements
JSON All of v2.1.292
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.292,
ImprovementsSection of the release
What

Stdio MCP servers (tool servers that run as a local program on your machine) now use automatic protocol negotiation, where Claude Code probes the server to agree on a protocol version. They fall back to the older handshake only when the server-side setting comes back explicitly off. Before, with no value from the server, they used the older handshake. The setting has read on for this site's account and for the anonymous baseline since 2026-09-29.

Other details:

  • In automatic mode, stdio servers can skip an earlier check that probed the older listing method
  • HTTP servers already used negotiation by default
  • claude.ai proxy and remote proxy connections still fall back to the older handshake
  • The log line for the older HTTP and server-sent events fallback now says "this server" instead of "this connector"
Why

Local MCP servers may now connect with the newer protocol directly, without going through the older probe first.

Read from
Feature flag
tengu_mcp_protocol_negotiation_stdio On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.292: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

tengu_mcp_legacy_sse_fallback Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.292: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.292. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_mcp_protocol_negotiation_stdio, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_mcp_protocol_negotiation_stdio, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.292 →

Feedback