Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.274 ·

MCP server 'source' attribution (sdk / plugin / config scope) added to schemas

MCP server status now reports where each server definition came from

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

MCP (Model Context Protocol) server status information now includes an optional source field, showing whether a given server was registered in-process via the SDK, came from a plugin, or came from a config scope such as user, project, local, dynamic, managed, enterprise, claudeai, or agent. This is computed internally from the server's metadata and exposed on mcp_servers status entries.

Why

This lets you (or tools reading this status) tell where an MCP server definition actually originated, rather than relying on its name alone, which is useful when the same server name could be defined in more than one place.

See this entry in the whole of v2.1.274 →

Feedback