{"version":"2.1.296","anchor":"mcp-client-capabilities-drop-elicitation-tasks-capability","canonical_anchor":"mcp-client-capabilities-drop-elicitation-tasks-capability","heading":"MCP servers are no longer told Claude Code takes background-task input requests","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/mcp-client-capabilities-drop-elicitation-tasks-capability","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### MCP servers are no longer told Claude Code takes background-task input requests\n\nClaude Code no longer tells MCP servers it can handle requests for your input as background tasks; it still supports plain input requests\n\n**What**\n\nMCP (Model Context Protocol) servers are outside programs that give Claude Code extra tools. When Claude Code connects to one, it lists what it supports. Some servers can ask you for input mid-task, which MCP calls elicitation.\n\nBefore, under a certain condition, Claude Code said it could take those input requests as background tasks. It no longer says so. It still advertises:\n\n- roots\n\n- elicitation\n\n- its extensions entry\n\n**Why**\n\nMCP servers will no longer see support for background-task input requests, so a server that relied on it should fall back to plain input requests.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}