Croway commented on PR #30343: URL: https://github.com/apache/camel/pull/30343#issuecomment-6981281232
Thanks @davsclaus and @oscerd. Changes in d1216f1: **1. `dual` as the default.** It was a deliberate choice, made for these reasons: - A client that opens with `initialize` takes exactly the session path of `legacy`. In `dual`, the only extra step is reading the protocol version from the body, and only a request that carries 2026-07-28 takes the new path. - The clients that try 2026-07-28 first (the TypeScript and Python SDK clients, Claude Code) fall back to `initialize` when a server does not serve it. So `legacy` costs them nothing, and `dual` only changes what they choose. - quarkus-mcp-server does the same: since 2.0.1 (Camel Quarkus 3.40) it serves 2026-07-28 next to sessions with no option. Camel Main and Camel Quarkus behave the same way by default. - "Preview" is about the SDK's Java API, which may still change before SDK 3.0 and which we absorb inside camel-mcp-server. The protocol revision is published, and `dual` passes its conformance suite (point 4). - `camel.server.mcp-protocol-era = legacy` is the documented opt-out in the upgrade guide. **2. Gateway sentence.** Agreed. `mcp-server.adoc` now says that the server compares `Mcp-Method` / `Mcp-Name` with the body only for 2026-07-28. A gateway that routes or authorizes on these headers must therefore reject requests without `MCP-Protocol-Version: 2026-07-28`, or the instances must run with `mcp-protocol-era = modern`. **3. `legacy` + `mcp-stateless` and `-32022`.** Agreed. The 2026-07-28 Streamable HTTP "Backward Compatibility" section reads a recognised modern error as a 2026-07-28 server. Such a request now gets HTTP 400 and `-32600` naming the versions the stateless transport serves (2025-03-26, 2025-06-18, 2025-11-25, so no more 2024-11-05). That is what `legacy` with sessions answers, so a client that also speaks an older version falls back to `initialize`. The doc sentence and the test are updated. This also makes oscerd's fallback point hold for every client, not only those that treat a `-32022` listing only older versions as a fallback signal (the TypeScript client does). **4. Conformance on `dual`.** Added `OfficialMcpDualConformanceIT`: the 2026-07-28 suite against the default `dual`, with the same baseline as `modern`. The existing `OfficialMcpConformanceIT` (older versions) already runs against the default, so `dual` is now covered by both suites. All three pass locally (`-Dofficial-mcp-conformance`). **6. JIRA summary.** CAMEL-27145 is now "camel-mcp-server - serve MCP protocol version 2026-07-28, and optionally without sessions". The PR description is updated. _Claude Code on behalf of Croway_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
