Wanaku — MCP Router + Gateway for Agents

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.