{"version":"2.1.305","anchor":"mcp-initialize-capabilities-are-reduced-for-hosts-flagged-by","canonical_anchor":"mcp-initialize-capabilities-are-reduced-for-hosts-flagged-by","heading":"Claude Code advertises fewer MCP features to some servers","tier":"soon","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/mcp-initialize-capabilities-are-reduced-for-hosts-flagged-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Claude Code advertises fewer MCP features to some servers\n\nFor MCP servers whose host is flagged by the cloud host check, Claude Code now trims the features it says it supports when connecting\n\n**Unclear.** Which features are removed from the list is not known.\n\n**What**\n\nWhen Claude Code connects to an MCP server, an add-on tool provider, it first sends a list of the features it supports. This list is called its capabilities. Before, the list depended only on the kind of connection.\n\nNow, when the server's host is flagged by the cloud host check, Claude Code trims that list before sending it. This happens in the first connection exchange, in the auto mode handler, and during client setup. Claude Code also declares its task support before the list of servers.\n\n**Why**\n\nIt changes what Claude Code tells certain MCP servers it can do.\n\n- Flag `tengu_gleaming_creek`: Not enough to say (read for one account on one subscription tier against v2.1.305; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) 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.\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}