[FEATURE] MCP elicitation support in Claude Desktop app

Resolved 💬 2 comments Opened Mar 31, 2026 by yurikotikov Closed Apr 3, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code CLI supports MCP elicitation (elicitation/create), but the Claude Desktop app does not. Per the MCP client capabilities matrix, elicitation is only available in the CLI.

Are there plans to bring elicitation support to the Desktop app?

Proposed Solution

#### Specifically needed

  • Form mode — structured input (confirmations, selections, non-sensitive text fields)
  • URL mode — for sensitive credentials like API keys, where data must not transit the MCP client

The MCP spec (2025-11-25) states:

> Servers MUST NOT use form mode elicitation to request sensitive information such as passwords, API keys, access tokens, or payment credentials.
>
> Servers MUST use URL mode for interactions involving such sensitive information.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

MCP server integration

Use Case Example

We're building an MCP server that manages configuration profiles. Several workflows require user input mid-operation:

  1. Destructive change confirmation — Before deleting any configuration, the server needs to ask "Are you sure you want to delete? This cannot be undone." Without elicitation, the server must either proceed without confirmation (unsafe) or refuse the operation entirely

(poor UX).

  1. Option selection — When creating a new configuration, the server needs the user to pick from available vendor . The LLM guesses instead of letting the user choose explicitly.
  1. Vendor API key collection — Configuring a connection requires third-party API keys . Per the MCP spec, these MUST use URL mode elicitation so credentials never transit the MCP client. Currently impossible.

Without elicitation, the server cannot ask the user for confirmation or input during a tool call. The LLM must guess or the workflow breaks.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗