{"version":"2.1.293","anchor":"auto-mode-classifier-context-from-sdk-mcp-tools-excludes-pro","canonical_anchor":"auto-mode-classifier-context-from-sdk-mcp-tools-excludes-pro","heading":"Project-level SDK MCP tools no longer feed context to auto mode's checker","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/auto-mode-classifier-context-from-sdk-mcp-tools-excludes-pro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Project-level SDK MCP tools no longer feed context to auto mode's checker\n\nTools from SDK MCP servers set up at the project level no longer pass extra context to the check that approves actions in auto mode\n\n**What**\n\nIn auto mode, Claude Code uses a checker, called a classifier, to decide whether an action can go ahead without asking you. Some tools can pass extra context to that checker. MCP (the Model Context Protocol) is how Claude Code connects to outside tools, and some MCP servers are supplied through the SDK, the toolkit for building on Claude Code.\n\nTools from SDK MCP servers still pass that context, but no longer when the server is set up at the project level, meaning configured for one project rather than for you as a user.\n\n**Why**\n\nA server tied to a project could come from that project's own files. Stopping those servers from adding context to the checker means they cannot influence what auto mode allows.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}