tengu_mcp_url_elicitation
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.281, including the newest one read.
MCP server configs accept a new bareElicitationCapability option that gives the server the plain elicitation capability instead of the legacy URL one
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.281.
In the changelogs
6Releases whose published page names tengu_mcp_url_elicitation.
-
v2.1.319
MCP task input errors no longer repeat the server's own text
Errors about MCP task input requests now list only fault codes, not the text or input key the server sent
gate cited by this entry
-
v2.1.300
MCP tasks that need a link request are cancelled when link requests are off
If link requests are switched off, an MCP task that asks for input by link is now cancelled instead of being handled
gate cited by this entry
-
v2.1.287
MCP servers on common connection types now get link and form requests by default
Claude Code now defaults to offering link and form input requests to MCP servers on stdio, sse, http or ws connections
gate cited by this entry
-
v2.1.283
MCP servers on older Java SDKs now connect after one automatic retry
If a Java MCP SDK 0.17.0-or-older server rejects Claude Code's elicitation support, Claude Code reconnects once without the parts it rejects
gate cited by this entry
-
v2.1.281
New
bareElicitationCapabilityMCP server optionMCP server configs accept a new
bareElicitationCapabilityoption that gives the server the plain elicitation capability instead of the legacy URL onegate cited by this entry
-
v2.1.281
New MCP server config key
bareElicitationCapabilityonly matters behind legacy elicitation gate (fallback off)MCP server configs accept
bareElicitationCapability, which only has an effect behind thetengu_mcp_legacy_url_elicitationgategate cited by this entry
Gate readings
5| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.319 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.300 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.287 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.283 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.281 read on another version | Not enough to say | no value returned | no value returned | on |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
First cited
1The earliest release whose published evidence quoted tengu_mcp_url_elicitation was v2.1.300, 14 Oct 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
38One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.