Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

MCP tool hooks can now run on connector servers

A new takesMcpToolHooksOnConnectors setting lets mcp_tool hooks target connector servers, and hook listings show more detail

Use it now Notable New Features
JSON All of v2.1.319
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
New FeaturesKind: in v2.1.319,
What probably matters to youSection of the release

Unclear Whether takesMcpToolHooksOnConnectors can be set in your own settings or only comes from a managed or remote source is unclear.

What

Hooks 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.

Hook listings now also report:

  • Whether a hook is held
  • Whether it runs on connectors
  • Whether it differs from another copy
  • Whether it was judged

When a plugin's hooks are held back, the listing now gives a reason, such as hooks_module, other_copy or load_error.

Why

MCP tool hooks can run in more places, and you can now see why a hook was held back.

Read from
Names in the bundletakesMcpToolHooksOnConnectorsmcp_tool
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether takesMcpToolHooksOnConnectors can be set in your own settings or only comes from a managed or remote source is unclear.

See this entry in the whole of v2.1.319 →

Feedback