MCP input requests
Also called: input_required, multi-roundtrip requests, MRTR
Some MCP operations need additional information before returning their final result. In the inspected 2026-07-28 revision, a tool call, resource read or prompt retrieval can return resultType input_required with named input requests. The client gathers the requested input and retries the original operation with corresponding inputResponses.
For example, an export tool could ask the user to choose a destination folder. The retry carries that choice and any opaque requestState supplied by the server. The server must validate returned state rather than trust it because it passed through the client. This is a sequence of independent client-initiated exchanges, not a separate server-initiated JSON-RPC request awaiting a reply.
- Read first
- Model Context Protocol
- Related
- MCP tool invocation, MCP prompts, MCP resources
- Further reading
- MCP — multi-roundtrip requests, revision 2026-07-28