Unclear It is not settled which mode applies when nothing sets require_connector_block_on_plugin_servers, so whether blocking is enforced by default is unclear.
What
MCP servers give Claude extra tools. Plugins can bring their own, and an organization can block claude.ai connectors.
- A plugin MCP server whose address matches a connector the organization blocked can now be blocked. The flag
require_connector_block_on_plugin_serversselects the mode. - Modes include "on", which blocks, and "count_only", which only counts matches. Others are "fault", "unattributed" and "off".
- In "on" mode, sign-in fails with "MCP OAuth refused: connector block" or "MCP OAuth refused: connector check failed".
- Sign-in waits for the connector list and fails with a timeout message if it is slow.
- In "count_only" mode, if recounting fails the message is "The connector block's count after a policy answer failed".
- The connector list can still be turned off with
ENABLE_CLAUDEAI_MCP_SERVERSor thedisableClaudeAiConnectorssetting, now through one check with unchanged behaviour.
Why
Organization admins can stop plugins from reconnecting a blocked service. If a plugin server stops connecting, an organization block may be the reason.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not settled which mode applies when nothing sets `require_connector_block_on_plugin_servers`, so whether blocking is enforced by…