# What are multi round-trip requests (MRTR) in MCP?

Multi round-trip requests (MRTR) are how an MCP server asks for more input in the middle of a call under the 2026-07-28 spec: it returns a result marked "input required", and the client calls again with the answers, instead of the server sending its own request over a held-open stream.

## Before and after

Earlier versions let a server send requests to the client, such as `elicitation/create` to ask the user a question, over a stream kept open for the session. The 2026-07-28 spec removed sessions, so instead the server answers with `resultType: "input_required"`, and the client retries the call with `inputResponses`.

Elicitation still exists as a client feature: it's how a server asks the user for information or confirmation, delivered through this pattern. See [migrate to the 2026-07-28 spec](https://ai-powered.com/academy/build-mcp-servers/migrate-to-2026-07-28).

## Sources

Official documentation, checked on 19 November 2026:

- [The 2026-07-28 specification release (MCP blog)](https://blog.modelcontextprotocol.io/posts/2026-07-28/)
- [MCP architecture overview (modelcontextprotocol.io)](https://modelcontextprotocol.io/docs/learn/architecture)

## Related terms

- [MCP](https://ai-powered.com/academy/glossary/mcp): MCP (Model Context Protocol) is an open standard for connecting AI applications to outside tools and data. An AI app connects to small programs called MCP servers, asks each one what it offers, and calls those tools when a task needs them.
- [Tool call](https://ai-powered.com/academy/glossary/tool-call): A tool call is a structured request from an AI model to run one of the functions it was given, with arguments that match the function's input schema. The app runs the function, sends the result back to the model, and the model uses it to answer or to decide its next step.
