Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · mcp

Elicitation changedspecification/2025-06-18/client/elicitation

Nearest release: v2.1.305, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 20 Oct 2026 20:02 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 20:07 UTC.

Upstream edited
Recorded here
Lines+14added
Lines−16removed
From line 1 where the diff opens
First seen 26 Aug 2026 this site's first read of the page
Recorded edits2to this page, all time

The whole hunk

from line 1, old and new numbered
/
lines
from line 1
11# Elicitation
22 
3<div id="enable-section-numbers" />
3> [!NOTE]
4>
5> Elicitation is newly introduced in this version of the MCP specification and its design may evolve in future protocol versions.
46 
5<Note>
6 Elicitation is newly introduced in this version of the MCP specification and its design may evolve in future protocol versions.
7</Note>
8 
97The Model Context Protocol (MCP) provides a standardized way for servers to request additional
108information from users through the client during interactions. This flow allows clients to
119maintain control over user interactions and data sharing while enabling servers to gather
from line 19
2119their needs—the protocol itself does not mandate any specific user interaction
2220model.
2321 
24<Warning>
25 For trust & safety and security:
26 
27 * Servers **MUST NOT** use elicitation to request sensitive information.
28 
29 Applications **SHOULD**:
30 
31 * Provide UI that makes it clear which server is requesting information
32 * Allow users to review and modify their responses before sending
33 * Respect user privacy and provide clear decline and cancel options
34</Warning>
22> [!WARNING]
23>
24> For trust & safety and security:
25>
26> * Servers **MUST NOT** use elicitation to request sensitive information.
27>
28> Applications **SHOULD**:
29>
30> * Provide UI that makes it clear which server is requesting information
31> * Allow users to review and modify their responses before sending
32> * Respect user privacy and provide clear decline and cancel options
3533 
3634## Capabilities
3735 
Feedback