{"version":"2.1.221","anchor":"mcp-sdk-handles-input-required-over-multiple-round-trips","canonical_anchor":"mcp-sdk-handles-input-required-over-multiple-round-trips","heading":"MCP SDK handles input_required over multiple round trips","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-sdk-handles-input-required-over-multiple-round-trips","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP SDK handles input_required over multiple round trips\n\nMCP tools that ask for extra input are now answered automatically, up to ten back-and-forth rounds.\n\n**What**\n\nTool and request results marked `resultType: \"input_required\"` are now satisfied automatically by the client, which fulfils the server's input requests through registered handlers and re-issues the call.\n\n**Details**\n\n- Defaults are autoFulfill on and a cap of 10 rounds.\n- Exceeding the cap fails with a message naming `inputRequired.maxRounds`.\n- Error text points at the alternatives, `allowInputRequired: true` or enabling `inputRequired.autoFulfill`.\n- Claude Code never passes an `inputRequired` option, so the defaults always apply.\n\n**Evidence**\n\n`rounds (inputRequired.maxRounds)`\n\n- Area: MCP\n- Names: `inputRequired.maxRounds`, `inputRequired.autoFulfill`, `allowInputRequired`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}