Croway opened a new issue, #8949: URL: https://github.com/apache/camel-quarkus/issues/8949
Quarkus runtime of [CAMEL-24308](https://issues.apache.org/jira/browse/CAMEL-24308) (camel-mcp-server): a JVM-only extension providing an `McpServerEngine` over the quarkiverse [quarkus-mcp-server](https://github.com/quarkiverse/quarkus-mcp-server) programmatic `ToolManager` API, so `ai-tool` routes are exposed as MCP tools over streamable HTTP. - Depends on `camel-mcp-server-api` (the runtime-agnostic bridge + SPI) — not the `camel-mcp-server` Vert.x engine used on Camel Main/JBang, so the MCP Java SDK and Reactor never reach the Quarkus classpath. - Bridge-owned options as `quarkus.camel.mcp-server.*` (enabled/tags/tool-timeout); serving concerns (path, transports, dev UI, auth, guardrails) stay fully owned by `quarkus.mcp.server.*`, per the precedence rule recorded on [CAMEL-24311](https://issues.apache.org/jira/browse/CAMEL-24311). - Requires camel 4.22 (`camel-mcp-server-api` is new in 4.22), so this targets the `camel-main` branch. _Claude Code on behalf of Federico Mariani_ -- 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]
