{"version":"2.1.321","anchor":"mcp-servers-gated-by-claude-in-chrome-policy-before-connect","canonical_anchor":"mcp-servers-gated-by-claude-in-chrome-policy-before-connect","heading":"MCP connections are checked against your organization's Claude in Chrome policy","tier":"notice","area":"MCP","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-servers-gated-by-claude-in-chrome-policy-before-connect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### MCP connections are checked against your organization's Claude in Chrome policy\n\nClaude Code now checks MCP servers against the organization's Claude in Chrome policy before and after connecting, and skips refused ones\n\n**Unclear.** Whether this check applies to every MCP server or only to the Claude in Chrome one is not clear.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Before connecting to one, Claude Code now checks it against your organization's policy for Claude in Chrome. This includes servers supplied by a program that runs Claude Code through the SDK, which used to connect without any such check.\n\n- If the policy refuses the server, Claude Code skips the connection and marks it as failed.\n\n- If the policy cannot be read, the server is also marked as failed, with a message saying Claude Code will try again.\n\n- After connecting and listing the server's tools, Claude Code checks it against the policy again.\n\n**Why**\n\nAn organization's Claude in Chrome policy now blocks the Chrome MCP server more strictly. If a server fails to connect, a policy refusal or an unreadable policy may be the cause.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}