MCP ConfigsMay 14, 2026·2 min read

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.

MCP Hub
MCP Hub · Community
Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage
Agent surface
Any MCP/CLI agent
Kind
Mcp Config
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Safe staging command
npx -y tokrepo@latest install 8ca53083-13f4-542a-b6e3-e6f4f4dc7868 --target codex

Stages files first; activation requires review of the staged README and plan.

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

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets

gh-aw-mcpg — MCP Gateway for Sandboxed Agents

gh-aw-mcpg is a Docker-first MCP gateway that exposes backend MCP servers over HTTP so sandboxed agents call tools through one controlled entrypoint.

MCP Configs
MCP Hub

MCP Gateway & Registry — Team Tool Control

MCP Gateway & Registry centralizes MCP servers and agent tools with auth, search, and audit, so teams can manage integrations and scan servers before use.

MCP Configs
MCP Hub

ContextForge — MCP Registry + Proxy Gateway

ContextForge runs an MCP gateway that federates tool servers behind one endpoint, adding governance, auth, and observability for agent tool calls.

MCP Configs
MCP Hub

SmartDB_MCP — Universal Database MCP Gateway

Universal database MCP gateway (MySQL/Postgres/Oracle/SQL Server) with role-based SQL permissions + health checks; verified 79★, pushed 2025-09-14.

MCP Configs
MCP Hub
◈Home🔍Search👤Me