JiriOndrusek opened a new issue, #9300: URL: https://github.com/apache/camel-quarkus/issues/9300
### Describe the feature here Camel 4.23 adds the `ai-resource` component (CAMEL-24394): routes exposed as read-only MCP resources (`resources/list`, `resources/read`), selected by the same tags as `ai-tool`. Camel Quarkus does not support it yet, including on the `camel-main` branch: - There is no `camel-quarkus-ai-resource` extension. The `camel-ai-resource` jar still arrives transitively through `camel-mcp-server-api`. - `QuarkusMcpServerEngine` does not implement `supportsResources()`, `resourceAdded()` or `resourceRemoved()`. The bridge logs `Engine QuarkusMcpServerEngine does not serve MCP resources: ai-resource routes matching the configured tags are not exposed` and exposes nothing. - There is no `quarkus.camel.mcp-server.*` option for the resource read timeout (Camel has `resourceTimeout`). - The mcp-server extension description, synced from Camel, already says "Expose ai-tool routes as MCP tools and ai-resource routes as MCP resources". It appears in the runtime pom, `quarkus-extension.yaml` and the docs page. ### Impact Once Camel 4.23 lands on `main`, CQ advertises MCP resources that Quarkus apps cannot serve. Nothing is broken on `main` today: Camel 4.22 has no `ai-resource`. ### Open question: own extension or part of mcp-server? Runtime behavior is the same either way; the serving code belongs in `QuarkusMcpServerEngine`. - **Own extension:** findable (code.quarkus.io, CQ catalog, and `camel export --runtime=quarkus`, which maps by name), its own support status, and consistent with `ai-tool`. Costs users one more dependency. - **Inside mcp-server:** one dependency less. Needs a `CqCatalog` special case to list `ai-resource`, and a later split if Camel adds a second adapter. Related: #9299, CAMEL-24394 -- 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]
