{"version":"2.1.260","anchor":"new-artifact-publish-refusal-local-server-name-collision-wi","canonical_anchor":"new-artifact-publish-refusal-local-server-name-collision-wi","heading":"New artifact-publish refusal: local server name collision with first-party server","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-artifact-publish-refusal-local-server-name-collision-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New artifact-publish refusal: local server name collision with first-party server\n\nPublishing now refuses when a local MCP server name would conflict with a built-in server name.\n\nPublishing 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.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}