{"version":"2.1.314","anchor":"mcp-dont-ask-again-rebinding-and-server-owner-registratio","canonical_anchor":"mcp-dont-ask-again-rebinding-and-server-owner-registratio","heading":"\"Don't ask again\" for MCP tools can move older permissions to the server's name","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-dont-ask-again-rebinding-and-server-owner-registratio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### \"Don't ask again\" for MCP tools can move older permissions to the server's name\n\nChoosing \"don't ask again\" for an MCP tool may now move an older grant to the server's name, and warns you if that fails\n\n**Unclear.** It is not clear whether an internal check limits this behaviour to some sessions.\n\n**What**\n\nMCP (Model Context Protocol) servers give Claude Code extra tools. When you choose \"don't ask again\" for one of their tools, Claude Code can now move an older saved permission so it belongs to the server's own name. If that fails, the rule is not saved and you are told you will be asked again.\n\nClaude Code also now registers the MCP servers in your configuration at startup. If that fails, it tries again when their tools load.\n\n**Why**\n\nThis changes how MCP tool permissions are saved. If you see the warning, Claude Code will keep asking for that tool.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}