{"version":"2.1.310","anchor":"desktop-connector-name-refusal-is-now-reported-and-artifact","canonical_anchor":"desktop-connector-name-refusal-is-now-reported-and-artifact","heading":"Claude Code now reports MCP servers whose names match a desktop connector","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/desktop-connector-name-refusal-is-now-reported-and-artifact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Claude Code now reports MCP servers whose names match a desktop connector\n\nAn MCP server named like a desktop connector is now reported as refused, and artifact tool swaps report when an entry is not served\n\n**Unclear.** It is not clear whether such a server is actually blocked or only recorded.\n\n**What**\n\nAn MCP server is an outside tool or data source Claude Code connects to. When an MCP server's name matches a desktop connector, Claude Code now records that the name was refused. Separately, when Claude Code swaps in MCP tools for an artifact and the entry is not being served, it now gives that as the reason.\n\n**Why**\n\nThis suggests MCP servers using desktop connector names may be refused.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}