Control Plane
Gateway Provisioning
ATLAS is the control plane — it provisions services in Kong and agentgateway when you register a capability. Traffic flows directly through the gateways, never through ATLAS.
How does provisioning work?click to expand
1
Register — You add a capability (API, MCP server, or AI agent) through the registration form or API. You provide the endpoint URL and metadata.
2
Provision — ATLAS immediately provisions the capability in the appropriate gateway: REST/GraphQL/gRPC → Kong, MCP/A2A → agentgateway. No polling, no delay.
3
Live — Traffic routes directly through the gateway to your upstream service. ATLAS is never in the data path — it only told the gateway where to route.
Kong Gateway
UnreachableREST, GraphQL, and gRPC routing with auth plugins and rate limiting.
agentgateway
Not configuredMCP server federation and A2A agent routing.
Architecture
Developer / Service Owner AI Client (Cursor / Claude)
│ │
│ "Register my API" │ "Find sales analytics"
▼ ▼
┌─────────────────────────────────────────────────┐
│ ATLAS (Control Plane) │
│ │
│ Registration → provisions in Kong / agentgw │
│ Catalog → searchable inventory │
│ Governance → risk, classification, ownership │
│ ATLAS-as-MCP → discovery + context │
│ Connect wizard → config for all gateways │
└──────────┬──────────────────┬────────────────────┘
│ Provisions │ Provisions
▼ ▼
┌──────────────────┐ ┌──────────────────┐
│ Kong Gateway │ │ agentgateway │
│ (Data Plane) │ │ (Data Plane) │
│ REST/GraphQL/ │ │ MCP/A2A/LLM │
│ gRPC traffic │ │ traffic │
└────────┬─────────┘ └────────┬─────────┘
▼ ▼
Upstream APIs MCP Servers / Agents