# Wanaku — MCP Router + Gateway for Agents > MCP router/gateway that bridges MCP servers, uses 300+ Apache Camel components, and offers optional Keycloak auth; verified 112★, pushed 2026-05-14. ## Install Merge the JSON below into your `.mcp.json`: ## Quick Use ```bash jbang app install wanaku@wanaku-ai/wanaku wanaku auth login --url http://localhost:8080 wanaku tools list ``` ## Intro MCP router/gateway that bridges MCP servers, uses 300+ Apache Camel components, and offers optional Keycloak auth; verified 112★, pushed 2026-05-14. **Best for:** Teams that want a single MCP gateway to route tools/resources across multiple MCP servers **Works with:** Java 21+ runtime; Wanaku CLI (JBang install) + MCP clients that connect to the router (per README) **Setup time:** 15-35 minutes ### Key facts (verified) - GitHub: 112 stars · 38 forks · pushed 2026-05-14. - License: Apache-2.0 · owner avatar + repo URL verified via GitHub API. - README-backed entrypoint: `jbang app install wanaku@wanaku-ai/wanaku && wanaku --help`. ## Main - Treat it as an MCP control plane: centralize tool/resource routing instead of configuring every MCP client with many servers. - Start without auth for local testing, then enable Keycloak when you need multi-user governance and explicit permissions. - Leverage Camel connectivity for integrations: README highlights 300+ components—use them to bridge enterprise systems into MCP. - Scope namespaces: use multi-namespace support to keep team tools isolated and reduce accidental cross-tenant leakage. ### Source-backed notes - README positions Wanaku as an MCP router and MCP-to-MCP bridge/gateway. - README lists optional Keycloak-based auth and Kubernetes-native deployment posture. - README Quick Start installs the CLI via JBang and shows `wanaku auth login` + `tools list` basics. ### FAQ - **Do I need Kubernetes?**: No — README describes Kubernetes-native support, but you can run it locally for evaluation. - **Is auth required?**: No — README says Keycloak auth is optional; enable it when you need secured routing. - **What’s the minimum to try it?**: Install via JBang, then run `wanaku tools list` after logging in to your router URL. ## Source & Thanks > Source: https://github.com/wanaku-ai/wanaku > License: Apache-2.0 > GitHub stars: 112 · forks: 38 --- ## Quick Use ```bash jbang app install wanaku@wanaku-ai/wanaku wanaku auth login --url http://localhost:8080 wanaku tools list ``` ## Intro Wanaku 是 MCP Router：可做 MCP-to-MCP 网关/代理，集成 300+ Apache Camel 组件，并可选 Keycloak 鉴权；已验证 112★，更新于 2026-05-14。 **Best for:** 想用一个统一入口把多个 MCP server 的工具/资源做路由与管理的团队 **Works with:** Java 21+；README 提供 Wanaku CLI（JBang 安装）并说明可作为 MCP server 网关供客户端接入 **Setup time:** 15-35 minutes ### Key facts (verified) - GitHub：112 stars · 38 forks；最近更新 2026-05-14。 - 许可证：Apache-2.0；作者头像与仓库链接均已通过 GitHub API 复核。 - README 中可对照的入口命令：`jbang app install wanaku@wanaku-ai/wanaku && wanaku --help`。 ## Main - 把它当 MCP 控制平面：把工具/资源路由集中起来，而不是让每个 MCP 客户端配置一堆 server。 - 本地先无鉴权跑通，再在需要多人治理时启用 Keycloak，明确认证与授权边界。 - 用 Camel 生态做集成：README 提到 300+ 组件，可用于把企业系统接入 MCP 路由层。 - 用 namespace 做隔离：多命名空间能降低跨团队误调用与“工具串台”的风险。 ### Source-backed notes - README 将 Wanaku 定位为 MCP Router，并支持 MCP-to-MCP 网关/桥接。 - README 提到可选 Keycloak 鉴权，以及 Kubernetes 原生部署支持。 - README Quick Start 通过 JBang 安装 CLI，并演示 `wanaku auth login` 与 `tools list`。 ### FAQ - **必须用 Kubernetes 吗？**：不必须；README 提到 Kubernetes 原生支持，但评估阶段可先本地运行。 - **鉴权是必须的吗？**：不是；README 说明 Keycloak 鉴权是可选项，需要安全治理时再开启。 - **最小化怎么试？**：用 JBang 安装后，登录路由地址再执行 `wanaku tools list` 查看工具列表。 ## Source & Thanks > Source: https://github.com/wanaku-ai/wanaku > License: Apache-2.0 > GitHub stars: 112 · forks: 38 --- Source: https://tokrepo.com/en/workflows/wanaku-mcp-router-gateway-for-agents Author: MCP Hub