Wanaku 0.1.1 is out — bringing Apache Camel's 400+ integrations to AI agents via #MCP.
Service Catalogs let you package Camel routes as AI tools. Deploy to Kubernetes or run locally. Agents can now talk to JMS, Kafka, FTP, GitHub, and more.
| Website | https://www.orpiske.net/ |
| https://www.linkedin.com/in/orpiske/ | |
| E-book in 🇧🇷 | http://angusyoung.org/camel-passo-a-passo/ |
| Github | https://github.com/orpiske |
Why it matters: AI agents can now interact with legacy systems, enterprise middleware, and non-REST APIs — all through battle-tested Apache Camel patterns.
No custom glue code. Just YAML and the Wanaku CLI.
New in 0.1.1:
✅ Service Templates (reusable integration blueprints via Camel Property Placeholders)
✅ CLI workflow: init → expose → package → deploy
✅ Kubernetes Operator + CRDs for declarative deployment
Built on #Quarkus. Open source. Fast.
Wanaku 0.1.1 is out — bringing Apache Camel's 400+ integrations to AI agents via #MCP.
Service Catalogs let you package Camel routes as AI tools. Deploy to Kubernetes or run locally. Agents can now talk to JMS, Kafka, FTP, GitHub, and more.
It has been a while since my last update on Wanaku, so I wrote a post about what’s on the radar for the next few versions. In short: maturing the project, stability and performance improvements.
It has been a while since I gave an update on Wanaku … Despite the lack of updates, our work continues on a steady pace 😅 During the 0.0.x series, our focus was on exploring new features, ideas, establishing a system architecture that would allow it to expand. In January we started the 0.1.x series: in this one we will focus on maturing what we created, evolving the router core, improving the stability and performance. Of course, we also will continue to explore new ideas, but now with a better understanding of the problem space. In light of this, here’s some stuff we have been working on for 0.1.0: - We have been working on a new e2e test framework to ensure greater stability between releases - We have fixed multiple UI and UX issues one the web front end - Bootstraping and managing security has been greatly simplified with a set of new management features - We have introduced a new runtime plugin for Camel integrations to connect to Wanaku without any further modifications to their code - We have started a multi-release effort to improve performance and scalability of Wanaku (0.1.0 will already bring multiple improvements in this area) We don’t have a date set for when 0.1.0 will be out, but the likely period should be around early April. Meet Wanaku at wanaku.ai. #MCP #AI
#AI systems don't need to feel like magic. Sometimes all you need is a boring, predictable and reliable system that you can rely on.
https://developers.redhat.com/articles/2026/02/04/making-llms-boring-chatbots-semantic-processors
🇧🇷 Pessoal, dia 27/01 vou participar de um bate papo no QuarkusClub sobre #ApacheCamel focado em um tema ainda pouco explorado: a infraestrutura de código por trás dos sistemas inteligentes.
This is truly mind blowing.

This is simply mind blowing.

🥳 Wanaku 0.0.8 is LIVE! 🥳
Biggest update: Visually design #ApacheCamel routes in #Kaoto & deploy as MCP Tools in #Wanaku on OpenShift! 🚀
Also: Full MCP Auth (OIDC), Streamable HTTP, & latest #Quarkus + #ApacheCamel.
Just published: Building a Real-Time RSS Integration with Quarkus + Apache Camel
- Stream and transform RSS feeds
- Persist as JSON
- Track authors & publications per month with Micrometer
Read here: https://www.the-main-thread.com/p/quarkus-camel-rss-integration-metrics