{"version":"2.1.311","anchor":"mcp-block-notices-mark-servers-that-claude-code-itself-block","canonical_anchor":"mcp-block-notices-mark-servers-that-claude-code-itself-block","heading":"MCP blocks now say when Claude Code itself did the blocking","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/mcp-block-notices-mark-servers-that-claude-code-itself-block","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### MCP blocks now say when Claude Code itself did the blocking\n\nMCP servers and tools blocked by Claude Code itself are now marked `byClaudeCode` and shown as \"disabled by Claude Code\"\n\n**Unclear.** It is not known whether the message you see about a blocked server changes.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Some are blocked by your organization's settings, and some are refused by Claude Code itself. These two cases are now told apart.\n\n- A server's `org_blocked` status now includes `byClaudeCode: true` when Claude Code itself refuses the server's configuration. Before, the status carried only the server name. How this changes the text on screen was not traced.\n\n- The MCP tools dialog now says \"disabled by Claude Code\" when a tool is blocked by Claude Code rather than by your organization. Before, it always said \"disabled by your organization\".\n\n- The message about deferred tools has a matching variant, including the wording \"Claude Code itself blocks this tool from MCP server\".\n\n**Why**\n\nYou can now see who blocked a server or tool. A block from Claude Code itself is no longer reported as an organization policy, so you know whether to ask an administrator or change the server's configuration.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}