{"version":"2.1.318","anchor":"hooks-mcp-tool-hooks-on-remote-machine-http-hooks-and-cond","canonical_anchor":"hooks-mcp-tool-hooks-on-remote-machine-http-hooks-and-cond","heading":"mcp_tool hooks can run on another machine, and hook conditions work more widely","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/hooks-mcp-tool-hooks-on-remote-machine-http-hooks-and-cond","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### `mcp_tool` hooks can run on another machine, and hook conditions work more widely\n\nAn `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\n\n**Unclear.** It is not clear when an `mcp_tool` hook runs on the other machine rather than locally.\n\n**What**\n\nAn `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.\"\n\nTwo related changes:\n\n- HTTP hooks that fail on the other machine are now logged.\n\n- 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.\n\n**Why**\n\nHooks now reach setups where the MCP server lives in a remote container rather than on your own computer.\n\n- Area: Hooks\n- Names: `mcp_tool`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}