{"version":"2.1.319","anchor":"hooks-mcp-tool-hooks-on-connectors-guardedjudged-hook-ent","canonical_anchor":"hooks-mcp-tool-hooks-on-connectors-guardedjudged-hook-ent","heading":"MCP tool hooks can now run on connector servers","tier":"use","area":"Hooks","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/hooks-mcp-tool-hooks-on-connectors-guardedjudged-hook-ent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### MCP tool hooks can now run on connector servers\n\nA new takesMcpToolHooksOnConnectors setting lets mcp_tool hooks target connector servers, and hook listings show more detail\n\n**Unclear.** Whether takesMcpToolHooksOnConnectors can be set in your own settings or only comes from a managed or remote source is unclear.\n\n**What**\n\nHooks are commands that run at set points while Claude Code works, and an `mcp_tool` hook calls a tool on an MCP server. Before, these hooks were only allowed on servers set up for the current project. The settings now accept `takesMcpToolHooksOnConnectors`, which lets them target connector servers as well.\n\nHook listings now also report:\n\n- Whether a hook is held\n\n- Whether it runs on connectors\n\n- Whether it differs from another copy\n\n- Whether it was judged\n\nWhen a plugin's hooks are held back, the listing now gives a reason, such as `hooks_module`, `other_copy` or `load_error`.\n\n**Why**\n\nMCP tool hooks can run in more places, and you can now see why a hook was held back.\n\n- Area: Hooks\n- Names: `takesMcpToolHooksOnConnectors`, `mcp_tool`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}