{"version":"2.1.242","anchor":"rules-for-naming-claude-ai-connectors-in-an-artifact","canonical_anchor":"rules-for-naming-claude-ai-connectors-in-an-artifact","heading":"Rules for naming claude.ai connectors in an Artifact","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/rules-for-naming-claude-ai-connectors-in-an-artifact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Rules for naming claude.ai connectors in an Artifact\n\nClaude now names claude.ai connectors by display name in Artifacts, and says connectors with odd characters must be renamed first.\n\n**What**\n\nWhen your session has claude.ai connectors attached, Claude now gets explicit rules for referring to them in an Artifact: use the connector's display name, \"never the id or any `mcp__` segment\", \"because viewers resolve connectors by name only\". Connectors with no name are described to you by the tools they offer, and connectors whose names contain anything beyond letters, digits, spaces and `. _ ( ) -` \"cannot be declared at all until renamed\" in claude.ai under Settings then Connectors.\n\n**Details**\n\n- The connector support itself already existed; this is new guidance that changes how Claude refers to and refuses connectors.\n\n**Evidence**\n\n`because viewers resolve connectors by name only`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}