Two weeks ago we introduced the Camel TUI – a terminal dashboard for monitoring and managing Apache Camel integrations. Since then, development has continued at a rapid pace. This post covers the latest additions landing in Camel 4.22. Open Any Project You can now launch the TUI directly from any existing Camel project – Spring Boot, Quarkus, or Camel Main – by pointing it at the project directory: camel tui .
Camel 4.22 brings two features that change how Camel integrates with AI: a unified tool abstraction (camel-ai-tool) and a built-in MCP server (camel-mcp-server). Together, they let you turn any Camel route into an AI tool that works across frameworks and protocols. This post covers both features. The Problem: Fragmented Tool Definitions Before 4.22, defining AI tools in Camel meant picking a framework and committing to it. Want to expose a route as a tool for LangChain4j?
Camel 4.21.0 shipped on 1 July with 32 security fixes. 4.18.3 followed on 3 July with 34, and 4.14.8 on 4 July with 27. All three supported release lines were patched inside four days, and every finding got a signed public advisory. A batch of 32 gets noticed, usually for the wrong reason. So I want to write about the process that produced it rather than walk through the list. If you are running Camel in production, the number of advisories in a release tells you very little.