{"version":"2.1.238","anchor":"artifact-publishing-rejects-connector-names-reserved-for-the","canonical_anchor":"artifact-publishing-rejects-connector-names-reserved-for-the","heading":"Artifact publishing rejects connector names reserved for the viewer's own servers","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/artifact-publishing-rejects-connector-names-reserved-for-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Artifact publishing rejects connector names reserved for the viewer's own servers\n\nPublishing an artifact with a reserved connector name now tells you exactly what to rename.\n\n**What**\n\nIf a published artifact declares a connector whose name is reserved for the viewer's local servers, publishing is now refused with a specific error telling you to rename it in claude.ai Settings, Connectors, rather than the older generic \"unresolved\" complaint. Publishing also retries when the server reports a rate limit that is not a recognised reset.\n\n**Details**\n\n- The error class is `reserved_mcp_server_name` and the report carries a count of reserved names; it is checked before the existing unresolved and over-cap classes.\n- A recognised reset condition produces a message telling the model the publish did not finish and to republish to the same slug after the reset, instead of sleeping and retrying.\n- Oversize, unobserved and merged-entry messages now say \"connector\" or \"local server\" depending on the entry.\n- The capability schema gained an optional per-surface features map.\n\n**Evidence**\n\n`a name reserved for the viewer's local `, `reserved_mcp_server_name`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}