Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.310 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.310entry #200

Claude Code v2.1.310 ·

MCP tool names are read more flexibly and server settings are checked by value

Claude Code now tries a second way to read MCP tool names and checks MCP server environment variables by their value as well as their name

Under the hood Internal Changes
JSON All of v2.1.310
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.310,
Internal ChangesSection of the release

Unclear Which MCP tool names or environment variable values are now accepted or rejected that were not before is not stated.

What

MCP (Model Context Protocol) is the way Claude Code connects to outside tools and services, called MCP servers. Several parts of how Claude Code handles them changed:

  • Tool names starting with mcp__ are now read by a second method when the first one cannot make sense of the name.
  • Environment variables set for an MCP server (settings passed to the server program when it starts) are now checked using their value as well as their name. Before, only the name was checked.
  • Two new labels for recording MCP errors or steps were added, one for standard keys and one for desktop connector names.
Why

This shifts how Claude Code recognises MCP tool names and which server environment variables it accepts, so a setup that relies on unusual tool names or variable values may behave differently.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich MCP tool names or environment variable values are now accepted or rejected that were not before is not stated.

See this entry in the whole of v2.1.310 →

Feedback