{"version":"2.1.281","anchor":"claudeai-mcp-enabled-in-chat-matching-is-case-insensitive","canonical_anchor":"claudeai-mcp-enabled-in-chat-matching-is-case-insensitive","heading":"Claude.ai MCP 'enabled in chat' matching is case-insensitive with a name fallback","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/claudeai-mcp-enabled-in-chat-matching-is-case-insensitive","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Claude.ai MCP 'enabled in chat' matching is case-insensitive with a name fallback\n\nMatching claude.ai connectors as enabled in chat now ignores letter case and falls back to the server's name when its ID header is missing\n\n**What**\n\nConnectors from claude.ai are MCP servers set up on your claude.ai account. When Claude Code works out which of them are enabled in chat, it now compares server IDs without regard to upper or lower case. If the `X-MCP-Server-ID` header is missing, it looks up the server's ID by its name.\n\n**Why**\n\nConnectors that differ only in capitalisation, or that arrive without an ID header, should now be recognised correctly as enabled.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}