Remuda Overview

Remuda is Federal Frontier’s MCP registry and router — the single governed endpoint where platform and customer tools are registered, namespaced, and exposed to agents.

Remuda is Federal Frontier’s MCP registry and router — the single governed endpoint where platform and customer tools are registered, namespaced, and exposed to agents.

It is the product name for the capability previously documented as the Frontier MCP Registry. Agents and operators talk to Remuda; they do not wire every runner to every backend MCP server.

Product vs engine

Layer Name Role
Product Remuda Federal Frontier MCP registry/router — namespaces, registration, agent-facing endpoint
Engine Wanaku Open-source MCP router/registry underneath (charts, upstream, operator)

Prefer Remuda in customer-facing docs. Mention Wanaku when discussing the engine, Helm charts, or upstream.

What Remuda is not

  • Not the Frontier Management Cluster (FMC) or VitroAI HCI — those are where Remuda runs (FMC or customer Kubernetes).
  • Not the SRE Investigator or posse roles — Investigators and SMEs consume Remuda namespace slices as harness shape.
  • Not a fleet of one-off agents.

Beachhead

Remuda is the Federal Frontier Platform beachhead: deploy on existing Kubernetes with the customer’s IdP / Keycloak. VitroAI is optional, not a prerequisite.

Runtime — what agents call

Remuda serves MCP over namespace paths. Examples used by the SRE Investigator:

  • /ns-9/mcp — SRE-slim tool slice
  • /public/mcp — wider / fallback slice

Operators register MCP servers as forwards. Tools are discovered and invoked through that one Remuda endpoint (OIDC / Bearer auth), instead of attaching every agent to every backend server.

Detailed registry architecture, Camel SoR path, and security posture remain on the Remuda / Frontier MCP Registry page.

Remuda Studio vs runtime

Surface Role
Remuda Studio Operator/product shell for MCP registration and wrapping agents (Lab develop/promote lives in Compass / Remuda Studio; promote/HIL remains OutpostAI)
Remuda runtime In-cluster router/registry that Jobs and runners actually call (MCP URL + auth + namespace)

Compass / Remuda Studio authors agents — the Agent Harness runs them.

How the SRE Investigator uses Remuda

The SRE Investigator is one OpenCode runner. Posse roles and the SME catalog select which Remuda namespace and first tools to expose — harness shaping (ADR-033), not a Remuda agent zoo.