{"version":"2.1.281","anchor":"url-mode-mcp-elicitations-keep-the-elicitation-id-only-when","canonical_anchor":"url-mode-mcp-elicitations-keep-the-elicitation-id-only-when","heading":"URL-mode MCP elicitations keep the elicitation ID only when a completion channel exists","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/url-mode-mcp-elicitations-keep-the-elicitation-id-only-when","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### URL-mode MCP elicitations keep the elicitation ID only when a completion channel exists\n\nLink-based MCP input requests keep their ID only when the client has a channel to report completion\n\n**What**\n\nAn MCP server (an add-on that gives Claude Code extra tools) can ask you for input by opening a link. This is called a url-mode elicitation. The request's `elicitationId` is now passed along only when the client has a completion channel, meaning a way to report back that you finished. Clients using the \"modern\" protocol version count as not having one.\n\n**Why**\n\nFor clients using the \"modern\" protocol version, link-based requests now arrive without their ID.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}