Publishing an Artifact page now refuses when a declared MCP server name would bind the Claude app's own built-in server while the session also has a local MCP server of that name. The refusal tells the user to rename or remove the conflicting local server, since the page may have been built against a server no viewer can reach.
New artifact-publish refusal: local server name collision with first-party server
Publishing now refuses when a local MCP server name would conflict with a built-in server name.
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Bug FixesKind: in v2.1.260,
Bug FixesSection of the release