{"version":"2.1.310","anchor":"new-mcp-error-source-and-question-brake-telemetry-category","canonical_anchor":"new-mcp-error-source-and-question-brake-telemetry-category","heading":"Two new MCP categories for desktop connector names and question pauses","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/new-mcp-error-source-and-question-brake-telemetry-category","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Two new MCP categories for desktop connector names and question pauses\n\nClaude Code now has two new MCP-related categories, one for desktop connector names and one called question brake\n\n**Unclear.** It is not clear what triggers the question brake or whether you would ever notice it.\n\n**What**\n\nMCP is the protocol Claude Code uses to connect to outside tools and servers. Two new names appear among Claude Code's MCP categories: `mcp_desktop_connector_name` and `mcp_question_brake`. The second sits next to an existing question pause category.\n\n**Why**\n\nIt hints at a new way of stopping MCP question flows.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}