MCP gateways, managed
The hosted MCPG platform: publish a gateway config and get a governed, observable MCP endpoint — identity, policy, and audit included — without running the fleet yourself.
Questions about your use case? Contact us — or book a demo and we'll walk through it live.
From config to endpoint in one publish
The same gateway you can self-host, run for you. The CLI drives everything; the console shows it.
mcpg cloud login --issuer https://auth.mcpg.cloud
mcpg cloud publish edge --config gateway.yaml
# … allocating → rendering → applying → ready
mcpg cloud instances # edge running https://edge.<zone>/mcpRe-publishing the same name updates the instance in place; every publish is a version you can diff and roll back to.
The managed surface, exactly as documented
Publish a config, get a gateway
One command turns a gateway config into a running, TLS-terminated MCP endpoint at your-name on our edge.
DocumentationVersioned configs and rollback
Every publish is a numbered version with a content hash. Diff any two, roll back to any of them in place.
DocumentationCustom domains
Serve your gateway on your own hostname with DNS-verified ownership and managed certificates.
DocumentationTenant administration
Organizations, workspaces, environments, memberships, and audit — the same tenancy model the self-hosted control plane ships.
DocumentationRegions and residency
Choose where your instances run; placement honors the region and residency domain you publish into.
DocumentationTunnels
Expose a gateway running inside your network through an outbound-only tunnel — no inbound firewall holes.
DocumentationRun it yourself, any time
mcpg.cloud runs the same open MCPG platform you can self-host: Apache-2.0 gateway and plugins, BUSL-1.1 fleet platform with an anti-resale grant — free for your own organization at any scale. No lock-in: your gateway config publishes here or on your own cluster, unchanged.