{"version":"2.1.318","anchor":"hook-schema-adds-takesmcptoolhooks-and-organizationlists-se","canonical_anchor":"hook-schema-adds-takesmcptoolhooks-and-organizationlists-se","heading":"Hook settings gain fields for MCP tool hooks and organization lists","tier":"notice","area":"Hooks","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/hook-schema-adds-takesmcptoolhooks-and-organizationlists-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Hook settings gain fields for MCP tool hooks and organization lists\n\nA hook capability description gains takesMcpToolHooks and organizationLists, and the init and maintenance matcher no longer names a trigger field\n\n**Unclear.** It is unclear whether either new field does anything yet for people writing hooks.\n\n**What**\n\nHooks are scripts you configure that Claude Code runs at certain moments. The description of what a hook can do has two new fields:\n\n- `takesMcpToolHooks`, optional\n\n- `organizationLists`, required\n\nThe hook documentation for the matcher with the values `init` and `maintenance` no longer says which field it matches against. It used to name the `trigger` field.\n\n**Why**\n\nThe names hint at hooks for MCP tools (tools from add-on servers) and at lists managed by an organization.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}