{"version":"2.1.63","anchor":"mcp-elicitation-hooks","canonical_anchor":"mcp-elicitation-hooks","heading":"MCP Elicitation Hooks","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.63\/e\/mcp-elicitation-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.63","markdown":"### MCP Elicitation Hooks\n\n**What**\n\nTwo new hook events that let hooks intercept MCP server elicitation requests (when an MCP server asks the user for input).\n\n**Details**\n\n- `Elicitation` hook fires when an MCP server requests user input. Hook can accept, decline, cancel, or provide content to auto-respond.\n- `ElicitationResult` hook fires after the user responds to an elicitation. Hook can override the response action or content.\n- Supports both form-based and URL-based elicitation modes\n- If a hook declines, the elicitation is blocked with \"Elicitation denied by hook\"\n\n**Evidence**\n\nHook event definitions (search for `\"Elicitation\"` and `\"ElicitationResult\"` near `hook_event_name`)"}