Frontier MCP Registry
Unified MCP tool routing for Federal Frontier Platform AI agents — powered by Wanaku and Apache Camel.
Frontier MCP Registry
The Frontier MCP Registry is the unified tool routing layer for all Federal Frontier Platform AI agents. It is powered by Wanaku — the first open-source Model Context Protocol router, built by the Red Hat Apache Camel team on Quarkus and Apache Camel.
Wanaku stands between autonomous AI agents and enterprise systems. Agents connect to a single MCP endpoint and discover all available tools, regardless of whether those tools are backed by native FFP-built MCP servers or Apache Camel routes connecting customer Systems of Record. From the agent’s perspective, every tool looks identical. The routing, authentication, and access control are invisible.
Two-Path Architecture
Path 1 — Native MCP Servers (FFP-built)
Federal Frontier Platform ships 16 purpose-built MCP servers covering the full federal infrastructure stack: Kubernetes, OpenStack (VitroAI), VMware, AWS, Ceph, Azure, Keycloak, ArgoCD, Gitea, Grafana, the Federal Frontier Ontology (FFO), Atlassian, Kolla, and Federal Compliance. These are registered as upstream proxies in Wanaku. Agents discover and invoke their tools through the single Frontier MCP Registry endpoint.
Path 2 — Customer SOR Integration via Apache Camel
Federal customers have existing Systems of Record — ServiceNow, vCenter, Splunk, SAP, IBM MQ, legacy CMDBs, mainframe systems — that contain authoritative data about their infrastructure. Where native MCP servers don’t exist, Apache Camel fills the gap. A Camel route is designed visually in Kaoto (VS Code extension), deployed to the Camel-K operator, and exposed as an MCP tool through a Wanaku rules file. Apache Camel provides 300+ enterprise connectors. An integration that would take weeks to build as a custom MCP server takes hours as a Camel route.
Token Efficiency
Pre-loading all tool definitions from 16 MCP servers into every agent session consumes approximately 37,500 input tokens per LLM call — roughly 80% of which are never used for any given task. The Frontier MCP Registry enables on-demand tool loading: the dispatch controller selects only the MCP servers relevant to the current alert type, reducing tool definition tokens per call by 77% — approximately $12,600 per year in Bedrock inference savings per FFP installation.
Security
All MCP tool invocations are authenticated via Keycloak OIDC (realm: FAS). OPA/Rego policies enforce role-based access control on tool invocation. Wanaku’s namespace isolation ensures that tools registered for one classification level are not visible to agents operating at a different level. Tool and resource definitions persist in an embedded Infinispan data grid — no external database dependency.
Open Standards
The Frontier MCP Registry is built entirely on open standards and open source: Model Context Protocol (Anthropic), Apache Camel (Apache Software Foundation), Wanaku (Red Hat / Apache Camel team), Quarkus, Keycloak, and OPA. No proprietary vendor lock-in at the integration layer.
Architecture
