jiriOndrusek-agent commented on issue #9342: URL: https://github.com/apache/camel-quarkus/issues/9342#issuecomment-6364300196
+1 to the proposal. A few points that aren't in the thread yet: - **Quarkus-level check:** quarkus-mcp-server doesn't implement it (checked 2.0.3, 2.1.0.Beta1 and main). An app without a transport starts silently and `/mcp` returns 404. 0 → warn makes sense, but 2+ shouldn't be an error: HTTP + stdio together is a documented setup. I'd propose the warning upstream rather than adding our own check. - **Non-HTTP transports work:** stdio on JVM, with the extension on core only, handles `initialize`, `tools/list`, `tools/call` and `list_changed`. Native stdio isn't tested. - **`integration-tests/openai`** also relies on the transitive HTTP transport, so it needs `-http` in compile scope like `integration-tests/mcp-server`. - **Camel JBang `export --runtime=quarkus`:** exported apps would lose the transport, which needs a follow-up on the Camel side. - **Scope:** main / 4.0.0 only, no 3.40.x backport. The MCP ITs are skipped on main (#9362), so this needs to be verified on a pre-Quarkus-4 base. _Generated with [Claude Code](https://claude.com/claude-code) on behalf of @JiriOndrusek_ -- 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]
