{"version":"2.1.257","anchor":"mcp-late-tool-addition-rejections-now-sticky-reject-a-beta-u","canonical_anchor":"mcp-late-tool-addition-rejections-now-sticky-reject-a-beta-u","heading":"MCP late tool-addition rejections now sticky-reject a beta until \/clear or \/compact","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/mcp-late-tool-addition-rejections-now-sticky-reject-a-beta-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### MCP late tool-addition rejections now sticky-reject a beta until \/clear or \/compact\n\nWhen an MCP server rejects a late tool addition, the beta stays rejected until you run \/clear or \/compact.\n\nWhen an MCP server rejects a tool addition with `header_rejected`, `block_type_unknown`, or `model_unsupported`, Claude Code now logs a warning, falls back to the ToolSearch announcement path, and sticky-rejects the corresponding beta for the rest of the session until `\/clear` or `\/compact`, rather than retrying it repeatedly.\n\n- Area: MCP\n- Names: `\/clear`, `\/compact`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}