What is MCP elicitation?
MCP elicitation is how an MCP server asks the person for more information in the middle of a request, through the client. In form mode the server sends a small JSON schema and the client renders a form; in URL mode it sends a link the person opens in a browser, for secrets the client must never see.
Part of Glossary: the terms behind MCP, coding agents and shared pages, defined plainly.
The client declares which elicitation modes it supports, form or url, in each request's _meta. The server may only use a mode the client declared.
Mid tools/call, the server needs something from the person. It returns an InputRequiredResult holding an elicitation/create request: a message and a schema.
{ "method": "elicitation/create", "params": { "mode": "form", "message": "Which environment?", "requestedSchema": { "type": "object", "properties": { "env": { "type": "string", "enum": ["staging", "production"] } }, "required": ["env"] } } }The schema is a flat object of strings, numbers, booleans and enums, with optional defaults and formats like email. The client builds and validates a form.
The person accepts, declines or cancels. The client retries the original request with the result in inputResponses, echoing any requestState the server sent.
In URL mode the client shows the full URL, asks for consent, opens a browser, then retries. The server sees the outcome; no secret passes through the client.
Source: MCP specification: elicitation
Form mode versus URL mode
A tool often cannot finish because it is missing one fact: which branch, which account, whether you really meant to delete that. Before elicitation, servers guessed, failed, or forced that fact into the tool's arguments and hoped the model would ask. Elicitation lets the server pause the request and put a question in front of the person.
Form mode keeps the question inside the client. The server sends a message and a requestedSchema, deliberately restricted: a flat object whose properties are strings, numbers, integers, booleans, or enums, single or multi-select, with optional titles, defaults, min and max, and string formats of email, uri, date and date-time. No nesting, no arrays of objects. The limit exists so every client can render the form without a full schema engine.
URL mode takes the interaction out of the client entirely. The server sends a url and a message; the client shows the whole URL, gets consent, opens it in a browser, and the person does whatever the page asks. The client learns nothing except that the person agreed to open it. This mode arrived in 2025-11-25 and is the only one allowed for secrets.
Example: asking which environment to deploy to
A deploy tool is called with no target. In 2026-07-28 the server answers the tools/call with an InputRequiredResult: resultType is input_required, inputRequests holds an elicitation/create with the message "Which environment?" and a schema containing one required string property, env, whose enum is ["staging", "production"]. It may add an opaque requestState so it can pick up where it left off.
The client renders two radio buttons. The person picks staging and submits. The client retries tools/call with a new request id, the same arguments, inputResponses containing {"action": "accept", "content": {"env": "staging"}}, and the untouched requestState. The server deploys and returns the normal result. If the person closes the dialog instead, the action is cancel, and the server decides whether to ask again next time.
In 2025-11-25 the server sent elicitation/create as its own request over the connection, and URL mode carried an elicitationId plus a notifications/elicitation/complete signal. The 2026-07-28 revision removes both: the client learns the outcome by retrying, and the server correlates with requestState.
Why it matters
Elicitation is what makes a tool safe to call with incomplete arguments. The model does not have to invent a value, and the server does not have to fail. It also draws a hard line around secrets: the spec says a server must not request passwords, API keys, access tokens or payment credentials in a form, and must use URL mode for them, so they never enter the model's context, the client's logs, or any server in between.
For the client, the rules are about trust. It must say which server is asking, must offer decline and cancel, must let the person review a form before sending, and for URL mode must display the full URL, never pre-fetch it, and never open it without consent.
Common mistakes
- Treating URL mode as sign-in to the MCP server. It is not. The client's own token comes from MCP authorization and stays the same. URL mode is for the server obtaining something from a third party on the person's behalf.
- Putting data in the URL. The spec forbids credentials or personal data in an elicitation URL, and forbids pre-authenticated links, because a malicious client could reuse them.
- Ignoring the phishing case. The person who opens a URL mode link must be the same person who triggered it; the server has to verify that, usually through its own signed-in session.
- Asking when the client cannot answer. A server must not send a mode the client did not declare. An empty elicitation capability means form mode only.
FAQ
- Can MCP elicitation ask for a password or API key?
- Not through a form. The spec says servers must not use form mode for passwords, API keys, access tokens or payment details, and must use URL mode instead, so the secret is typed into a page the server controls and never passes through the client or the model's context. Names and email addresses are allowed in forms.
- What happens when the user declines an MCP elicitation request?
- The client returns an action of decline, or cancel if the dialog was dismissed, with no content. The server has to cope: it might offer an alternative, fail the tool call cleanly, or ask again on a later attempt. The spec says a server must never assume an elicitation will succeed.
- Is MCP elicitation the same as MCP OAuth?
- No. MCP OAuth is how the client proves who it is to the server. URL mode elicitation is for a server that itself needs the person's consent or credentials for some other service. The client's token is untouched, and the server must not use elicitation to authorize users for itself.
Stop sending HTMLover Slack.
Create an account in a minute, connect your coding agent, and make your first board.