{"version":"2.1.251","anchor":"connector-names-accept-far-more-characters","canonical_anchor":"connector-names-accept-far-more-characters","heading":"Connector names accept far more characters","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/connector-names-accept-far-more-characters","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Connector names accept far more characters\n\nConnector names now allow almost any characters, with new checks against host-prefix and id-like names.\n\n**What**\n\nThe name you give a connector in a manifest is no longer restricted to letters, digits, spaces and a few punctuation marks. Any 1 to 64 characters are allowed except control characters, line breaks, unusual spaces and text-direction marks, and the name cannot start or end with a space or invisible character. A new check also rejects names that read like a `host:` prefix or like an internal id.\n\n**Details**\n\n- Names shaped like the internal `claude_ai_` or `mcp__` prefixes are rejected too.\n- The change swaps an allow-list for a deny-list, so accented and non-Latin names now pass.\n\n**Evidence**\n\n``must not read as \\`host:\\` or be shaped like an id or a \\`claude_ai_\\u2026\\`\/\\`mcp__\\u2026\\` prefix``\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}