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
HomeReleasesv2.1.317entry #50

Claude Code v2.1.317 ·

MCP server settings accept an optional displayName

An MCP server's settings can now include a displayName, and a badly formed value is ignored instead of breaking the config

Use it now New Features
JSON All of v2.1.317
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
New FeaturesKind: in v2.1.317,
What probably matters to youSection of the release
What

MCP servers are outside programs that give Claude Code extra tools. Their settings now accept an optional displayName text field. If the value is badly formed, Claude Code drops it rather than rejecting the whole server setting.

Why

It gives a server a field for a friendlier label, and a mistake in it will not stop the server from loading.

Read from
Names in the bundledisplayName
What the documentation says
Documented inapi/agents-and-tools/agent-skills/quickstart
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up displayName, on plugins-api. | `display_name`, `description`, `manifest_version` | The served version’s manifest `displayName`, `description`, and `version`; each is `null` when the manifest declares none. `description` might be a skill’s `description` rather than the… manage-claude/plugins-api see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up displayName, on plugins-api.

See this entry in the whole of v2.1.317 →

Feedback