Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

mcp_tool hooks can run on another machine, and hook conditions work more widely

An mcp_tool hook can now make its call on the machine that holds the MCP server, and hook "if" checks no longer require project settings

You'll notice Improvements
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.318,
What probably matters to youSection of the release

Unclear It is not clear when an mcp_tool hook runs on the other machine rather than locally.

What

An mcp_tool hook calls a tool on an MCP server when the hook runs. Claude Code can now make that call on another machine, the one that holds the server. If that machine does not reply properly, the hook fails with "The machine that holds the server gave no usable answer."

Two related changes:

  • HTTP hooks that fail on the other machine are now logged.
  • A hook's "if" condition no longer has to come from your project settings file to be checked. It now works for hooks from other settings sources too.
Why

Hooks now reach setups where the MCP server lives in a remote container rather than on your own computer.

Read from
Names in the bundlemcp_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 doubtIt is not clear when an `mcp_tool` hook runs on the other machine rather than locally.

See this entry in the whole of v2.1.318 →

Feedback