MCP servers now get URL and form elicitation by default

What

MCP servers are add-on programs that give Claude Code extra tools. Elicitation is a way for such a server to ask you for input, either with a form or by sending you to a web link (URL). This release changes when Claude Code tells a server it supports this:

• Default flipped: the fallback for the feature flag tengu_mcp_legacy_url_elicitation, the value used when the flag service sends nothing, is now true instead of false. The flag counts only when it is exactly true.
• What a server gets: when the flag is on, a server is offered the capability { form: {}, url: {} } instead of the plain client capabilities.
• Which servers: this applies only to servers whose type is unset, stdio, sse, http or ws, that do not have bareElicitationCapability: true, and that are not on the tengu_mcp_legacy_url_elicitation_server_denylist list. Servers on that list still get the plain capabilities.
• Second flag: tengu_mcp_url_elicitation (fallback true) must also be on for the form and URL capability to be added.
• HTTP servers: for servers reached over HTTP, connecting now wraps the network requests when this path is active, and keeps a way to switch that wrapper off.

In readings taken before this release, the flag service returned tengu_mcp_legacy_url_elicitation on for this site's account and for the anonymous baseline, switched on since the reading before. No reading has been taken under this release yet.

Why

Without a value from the flag service, eligible MCP servers are now told Claude Code can handle URL and form requests, so you may start seeing such prompts from servers that did not show them before.