{"version":"2.1.323","anchor":"mods-runtime-new-mcpconnect-and-toollist-hooks-and-a-plu","canonical_anchor":"mods-runtime-new-mcpconnect-and-toollist-hooks-and-a-plu","heading":"Plugins can now react to MCP connections and change the tool list","tier":"use","area":"Plugin Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mods-runtime-new-mcpconnect-and-toollist-hooks-and-a-plu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugins can now react to MCP connections and change the tool list\n\nPlugins gain `mcp.connect` and `tool.list` hooks, so they can step in on MCP connections and add or remove tools in a session\n\n**What**\n\nPlugins can now use two hooks, points where a plugin's code is run:\n\n- `mcp.connect`, when Claude Code connects to an MCP server (an add-on that supplies tools)\n\n- `tool.list`, when the list of tools Claude can use is built\n\nFor each session, Claude Code keeps track of what plugins answered, which tools they added or removed, and which hooks failed. If Claude tries to use a tool a plugin removed, the call is refused with a message saying a plugin removed it from this session.\n\n**Why**\n\nPlugins can shape which tools Claude sees and step in when MCP servers connect.\n\n- Area: Plugin Hooks\n- Names: `tool.list`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}