Croway opened a new issue, #9522:
URL: https://github.com/apache/camel-quarkus/issues/9522

   quarkus-mcp-server serves MCP protocol version 2026-07-28 (stateless: no 
`initialize` handshake, no `Mcp-Session-Id`) next to the protocol versions that 
open with `initialize`, on the same endpoint, choosing for each request from 
the protocol version it carries. Its stateless support is in the versions Camel 
Quarkus uses (2.0.3 on 3.40.x, 2.0.4 on `main`).
   
   The Camel routes registered by the `mcp-server` extension (`ai-tool`, 
`ai-resource`) should therefore reach a client of 2026-07-28 without any Camel 
configuration, which matters for restarts and for several instances without 
session affinity. This is not tested nor documented yet.
   
   Proposal:
   
   - an integration test with a 2026-07-28 client 
(`McpAssured...setStateless()`) and a raw request that creates no session, with 
its native counterpart;
   - a section in the extension documentation describing the two kinds of 
clients.
   
   On `main` the `mcp-server` tests are disabled until #9362 is resolved. On 
3.40.x the same test passes in JVM and native mode.
   
   Related: [CAMEL-27145](https://issues.apache.org/jira/browse/CAMEL-27145) 
(stateless MCP for Camel Main / JBang).
   
   _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]

Reply via email to