---
title: "MCP Elicitation vs ask_question: How Agents Ask"
description: "MCP elicitation asks you through the client as a form or URL. ask_question pushes the question to your phone and waits. How they differ and when to use each."
url: "https://notifexapp.com/blog/mcp-elicitation-vs-ask-question"
published: "2026-11-19"
updated: "2026-11-19"
author: "Alaa Jawhar"
---

# MCP Elicitation vs ask_question: Two Ways an Agent Asks a Human

MCP elicitation is the protocol's own way for a server to request input from the user, through the client, while it handles a request. The client shows a form or asks to open a URL, and passes the reply back. **ask_question** is a Notifex tool. The agent calls it, the question goes to your phone as a push, and your answer is the tool result. Elicitation needs you at the client. ask_question reaches you away from it.

Both let an agent ask a human and wait. They differ in who starts the question, where you answer it, and which clients support it. This post explains each one and when to pick which. Spec and client facts come from the official docs, read 2026-11-19.

## What is MCP elicitation?

The [MCP elicitation spec](https://modelcontextprotocol.io/specification/2026-07-28/client/elicitation) describes two modes. In **form mode** the server sends a message and a `requestedSchema`, and the client renders a form. In **URL mode** the server sends a URL for an interaction that must not pass through the client, such as a third-party sign-in.

Form schemas are kept small on purpose. They are flat objects with primitive fields only: string, number or integer, boolean, and enums for single or multiple choice. The user's reply comes back as one of three actions: `accept` with the content, `decline`, or `cancel`.

The spec also sets limits. Servers must not use form mode to ask for passwords, API keys, access tokens or payment details. Clients must show which server is asking and offer clear decline and cancel options.

![Two pages of the MCP specification: the Elicitation overview with form and URL modes, and an example form request with a requestedSchema.](https://d29bihfk9mha1v.cloudfront.net/notifex/blog-mcp-elicitation-vs-ask-question-el-1-v1.webp)

_MCP specification, version 2026-07-28, at modelcontextprotocol.io, captured 2026-11-19. Apps and logos belong to their owners._

## How does an elicitation request travel?

It depends on the protocol version. In the [2025-11-25 revision](https://modelcontextprotocol.io/specification/2025-11-25/client/elicitation), the server sends an `elicitation/create` request to the client while a tool call is open, and waits for the reply. In the 2026-07-28 revision, the server returns an `InputRequiredResult` that carries the request. The client collects the answer and retries the original call with the response attached.

Either way, the question lives inside one client session. If nobody is looking at that client, the request waits there.

## What does elicitation look like in a client?

In Claude Code, the [MCP docs](https://code.claude.com/docs/en/mcp) say an elicitation request opens an interactive dialog in the terminal, with no setup on your side. Form mode shows the server's fields. URL mode asks whether to open a link in your browser. Claude Code declares both modes for the servers in your own MCP configuration, from v2.1.287. For claude.ai connectors on the older revisions it declares form mode only.

We built a small demo server to see it. Its tool asks which build to prepare and whether to run migrations first. Claude Code showed the dialog below and waited for a choice.

![Claude Code showing an elicitation dialog from a demo MCP server named release-helper: which build to prepare, two build options, a migrations checkbox, and Accept or Decline.](https://d29bihfk9mha1v.cloudfront.net/notifex/blog-mcp-elicitation-vs-ask-question-el-2-v1.webp)

_Elicitation dialog from a demo MCP server. Claude Code 2.1.328 in a terminal on a Mac, demo project, captured 2026-11-19._

Support varies by client. The [Codex MCP docs](https://learn.chatgpt.com/docs/extend/mcp) did not mention elicitation when we read them. Check your client's docs before you design a server around it.

## What is ask_question?

ask_question is one of seven tools on the Notifex MCP server. The agent passes a question, a type and, for choices, a list of options. The types are single-select, multi-select and free text, with up to 20 options and an optional context note. It can attach images, video or PDFs that it uploaded first with create_upload.

By default the call blocks until someone answers, then returns the answer, who gave it and when. With `wait=false` it returns a question id at once, and the agent checks later with check_answer or waits with wait_for_answer. For a batch, ask_questions sends up to 10 questions in one push. In a team project every member gets the push, and the first answer wins.

_MCP elicitation vs Notifex ask_question (MCP spec 2026-07-28 and Notifex server code, checked 2026-11-19)_

|  | MCP elicitation | Notifex ask_question |
| --- | --- | --- |
| Who starts it | The MCP server, while it handles a request | The model, when it decides to call the tool |
| Where you answer | In the client: a terminal dialog, a desktop window or a card | On your iPhone or Android phone, after a push |
| Answer shapes | Flat form: text, numbers, booleans, single or multiple choice; or a URL | Single-select, multi-select or free text, with files attached |
| If you are away | The request waits in the client until you return | The push reaches you, and the call waits for your reply |
| Who can answer | The person at that client | Every member of the project; the first answer wins |
| Client support needed | The client must declare the elicitation capability | Any client that can call MCP tools |
| Secrets | Form mode must not ask for them; URL mode exists for that | Not meant for secrets either |

![A developer stands on a train platform answering a two-option question on her phone, while her empty desk at the office shows a form waiting on the monitor.](https://d29bihfk9mha1v.cloudfront.net/notifex/blog-mcp-elicitation-vs-ask-question-el-3-v1.webp)

_An elicitation form waits in the client on your computer. A push question reaches you wherever you are. Illustration._

## Who decides when to ask?

This is the main design difference. With elicitation, the server decides. A deploy server might always ask for confirmation before it ships, whatever the model thinks. With ask_question, the model decides, guided by your instructions in a file such as `CLAUDE.md` or `AGENTS.md`.

Server-side asking is stricter. Model-side asking is more flexible, because the agent can ask about anything: a branch name, a design choice, a release note. Many teams want both. The server guards its own risky step, and the agent asks about everything else.

## When is elicitation the better choice?

- **You sit at the client.** A terminal dialog is the shortest path when you are already there.
- **The server needs a value to finish its own job.** A missing field, a confirmation for a destructive call, or a choice only that server understands.
- **A third-party sign-in.** URL mode sends you to a browser page, so the credentials never pass through the client.
- **No extra app.** Nothing to install beyond the client you use.

## When does ask_question fit better?

- **You are away from the computer.** The question reaches your phone, and the agent waits.
- **The answer can take a while.** The question stays open, and a dropped connection can re-attach with wait_for_answer.
- **Someone else may answer.** In a team project the whole team gets the push.
- **You need to show something.** The agent attaches a screenshot or a PDF to the question.
- **Your client has no elicitation support.** ask_question is a plain tool call, so it works wherever MCP tools work.

## Can you use both in one setup?

Yes. They do not conflict. A client can connect to a server that elicits and to Notifex at the same time. In Claude Code, add Notifex with one entry, as shown on the [Claude Code setup page](https://notifexapp.com/claude-code). Other clients connect the same way, as listed on [the setup guide for each agent](https://notifexapp.com/connect-your-agent). Then install [the app on your iPhone](https://notifexapp.com/iphone-app) or [Android smartphone](https://notifexapp.com/android-app).

For the bigger picture of where a person should step in, see the [human-in-the-loop definition](https://notifexapp.com/glossary/human-in-the-loop) and [human in the loop vs human on the loop](https://notifexapp.com/blog/human-in-the-loop-vs-human-on-the-loop). The answer types are covered in [structured questions](https://notifexapp.com/features/structured-questions).

## Quick answers

### What is MCP elicitation?

It is the MCP feature that lets a server request input from the user through the client, as a form or a URL, while it handles a request.

### Does Claude Code support MCP elicitation?

Yes. Claude Code shows elicitation requests as a dialog in the terminal. Its docs say it declares form and URL modes for servers in your own MCP configuration.

### Can elicitation ask for an API key?

Not in form mode. The spec forbids form requests for passwords, API keys, tokens or payment details. URL mode exists for those flows.

### Is ask_question an MCP standard?

No. It is a regular MCP tool on the Notifex server. Any client that can call MCP tools can use it, without elicitation support.
