{"version":"2.1.286","anchor":"mcp-legacy-httpsse-fallback-now-guarded-by-a-second-elicita","canonical_anchor":"mcp-legacy-httpsse-fallback-now-guarded-by-a-second-elicita","heading":"Extra reconnect attempt for older Java MCP servers that reject elicitation","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mcp-legacy-httpsse-fallback-now-guarded-by-a-second-elicita","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Extra reconnect attempt for older Java MCP servers that reject elicitation\n\nIf an older Java MCP server rejects elicitation again after reconnecting, Claude Code now tries once more in legacy mode\n\n**Unclear.** It is not clear whether the second retry is reached in practice.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Elicitation is a feature that lets a server ask you for information through a form or a link. Servers built with Java MCP SDK 0.17.0 or older can reject that feature when Claude Code connects.\n\nBefore, Claude Code reconnected once without elicitation. Now:\n\n- the first rejection makes Claude Code redial straight away with a connection that leaves elicitation out\n\n- if the server rejects it again on that reconnect, Claude Code redials once more in legacy mode, the older HTTP plus SSE way of connecting\n\nThe legacy fallback is still controlled by the same remote setting as before.\n\n**Why**\n\nOlder Java MCP servers that refuse elicitation are more likely to connect instead of failing.\n\n- Flag `tengu_mcp_legacy_sse_fallback`: Not enough to say (read for one account on one subscription tier against v2.1.286; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}