Camel Quarkus 3.39 turns integration routes into MCP tools
The release adds native-friendly bridges for agent tools, embedding stores and declarative RAG ingestion while staying on Java 17 and 21.
Apache Camel Quarkus 3.39.0 gives Java integration teams a more direct path from an existing Camel route to an agent-facing tool. The official release notes list a new MCP server extension that can expose ai-tool routes through Quarkus MCP Server, alongside bridges for LangChain4j agents, named embedding stores and retrieval augmentation.
The release was published Aug. 24 and supports Java 17 and 21. It aligns Camel Quarkus with the Camel 4.22 line and the Quarkus 3.39 generation while preserving the project’s native-compilation focus.
What changed
The most consequential additions sit around retrieval-augmented generation and tool execution. A new langchain4j-ingest extension provides declarative document ingestion into an embedding store. Camel Quarkus can also discover named LangChain4j embedding-store beans, automatically bridge Camel ingestion into a registered AI service’s retrieval augmentor and apply a retrieval filter hook, according to the resolved-issue list.
For tool calling, the release adds support for Camel’s ai-tool concept and an MCP server integration that exposes those routes as MCP tools. The same issue list records a scoping fix after CamelAiToolProvider attached every registered tool to Camel LangChain4j agent endpoints, a useful reminder that tool discovery is also an authorization boundary.
The release also adds native support for Camel’s Micrometer observability component, hardens Jolokia defaults, exposes application properties in the Quarkus developer console and updates the IBM MQ Jakarta client to the 10.x line. The GitHub changelog also documents native-build fixes for AWS integrations and additional OpenTelemetry test coverage.
Who should care
Teams already using Camel Quarkus for APIs, messaging or event flows can now present selected integration capabilities to MCP clients without creating a separate tool-service layer. Teams building RAG applications get a more declarative ingestion path and tighter integration between Camel routes, embedding stores and Quarkus LangChain4j services.
That convenience does not remove the need to review which routes become callable. An MCP tool can trigger the same downstream systems and credentials as the route behind it.
What to do
Before upgrading, confirm that applications run on Java 17 or 21 and test native builds against the changed extensions. For MCP deployments, enumerate the routes intended for tool exposure, verify authentication and input validation at the boundary, and check that unrelated ai-tool routes are not discoverable. RAG users should test embedding-store selection and retrieval filters with production-like documents before moving ingestion into the new declarative path.
sources
- Apache Camel Quarkus 3.39.0 release notescamel.apache.org
- Apache Camel Quarkus 3.39.0 GitHub releasegithub.com
comments · 0