{"version":"2.1.284","anchor":"plugin-served-mcp-tool-error-names-the-mcp-server-correctly","canonical_anchor":"plugin-served-mcp-tool-error-names-the-mcp-server-correctly","heading":"Error for an unanswered plugin MCP tool call now shows the correct tool name pattern","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/plugin-served-mcp-tool-error-names-the-mcp-server-correctly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Error for an unanswered plugin MCP tool call now shows the correct tool name pattern\n\nWhen no `tool.call` hook answers a plugin-served MCP tool, the hint now builds the tool name from the MCP server's name, not the plugin's\n\n**What**\n\nPlugins can serve MCP tools, which are tools provided through an external tool server, and answer calls to them with a `tool.call` hook, their own code that runs when Claude uses a tool. When no hook answers a call, Claude Code shows a hint suggesting you add one, with the tool name pattern to match. That pattern starts with `mcp__`, then a name, then `__`. It now uses the MCP server's name there. It used to use the plugin's name.\n\n**Why**\n\nPlugin authors can copy the suggested pattern and have it match the tool.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}