{"version":"2.1.323","anchor":"org-mcp-policy-denial-is-surfaced-distinctly","canonical_anchor":"org-mcp-policy-denial-is-surfaced-distinctly","heading":"MCP servers blocked by your organization now say so","tier":"notice","area":"MCP","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/org-mcp-policy-denial-is-surfaced-distinctly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### MCP servers blocked by your organization now say so\n\nAn MCP server blocked by your organization's policy now says that, instead of the generic 'did not connect' message\n\n**What**\n\nAn MCP server is an outside program that gives Claude Code extra tools. When one failed, Claude Code always said it \"did not connect\". If the failure is because your organization's policy blocks it, Claude Code now says \"Your organization's MCP policy does not allow\" the server instead.\n\nA server that is turned off because something else is holding it also gets its own message now.\n\n**Why**\n\nIf your organization blocks a server, you can see that right away instead of trying to fix a connection problem that isn't there.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}