Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

MCP server settings now spot ${ variables in values rather than names

Claude Code now looks for ${ placeholders in the values of MCP environment variables and headers, not in their names

You'll notice Bug Fixes
JSON All of v2.1.317
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
Bug FixesKind: in v2.1.317,
Bug FixesSection of the release

Unclear It is not clear what Claude Code does differently with an entry once it finds ${ in the value.

What

MCP servers are outside tools that Claude Code connects to. Their settings can include environment variables (named values handed to a program when it starts) and headers (extra details sent with each request). Writing ${ in one of these marks a placeholder that Claude Code fills in from your own environment.

Claude Code used to look for ${ in the name of each entry. It now looks in the value instead, and only when that value is text.

Why

Placeholders are normally written in the value. This means Claude Code now notices them where they actually appear in an MCP server's settings.

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 doubtIt is not clear what Claude Code does differently with an entry once it finds `${` in the value.

See this entry in the whole of v2.1.317 →

Feedback