{"version":"2.1.309","anchor":"mcp-allow-rules-ignored-for-servers-whose-names-look-like-cl","canonical_anchor":"mcp-allow-rules-ignored-for-servers-whose-names-look-like-cl","heading":"MCP servers named like claude.ai connectors now explain why allow rules are ignored","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/mcp-allow-rules-ignored-for-servers-whose-names-look-like-cl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### MCP servers named like claude.ai connectors now explain why allow rules are ignored\n\nIf an MCP server's name starts like a claude.ai connector's, allow rules do not apply to it and Claude Code now says so\n\n**Unclear.** It is not clear exactly which server names count as starting like a claude.ai connector's.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. Allow rules are settings that let a tool run without asking you each time. When Claude Code sets up a tool from an MCP server, it now checks whether the server's name starts like the name of a claude.ai connector.\n\nIf it does, Claude Code logs this message: \"Allow rules do not apply: this server's name starts like a claude.ai connector's. To use allow rules, the server needs another name, and the rules must use that name.\"\n\n**Why**\n\nIf your allow rules stopped working for an MCP server, this message explains why. The fix is to rename the server and use the new name in your rules.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}