What is mcpg.cloud?

The hosted way to run MCPG — publish a validated gateway config and get a managed, observable MCP endpoint, without operating Kubernetes yourself. Config versioning, rollback, custom domains, and multi-tenant admin included.

mcpg.cloud is the managed version of MCPG. You bring a gateway config; the platform provisions and runs it as a managed MCP endpoint, keeps every published version, streams its logs and metrics, and lets you roll back or put it on your own domain. It is the same gateway and the same config as a self-hosted install — you just don't operate the cluster.

When to reach for the cloud

You want an MCP endpoint in minutes without standing up Kubernetes.
You'd rather publish a config than manage a Deployment, a ConfigMap, and a rollout.
You want config version history, one-command rollback, and hosted logs without wiring a pipeline.

If you need the gateway inside your own network or under your own compliance boundary, self-hosting runs the exact same software — nothing about a config is cloud-specific, so you can move either direction later.

How it works

The cloud is the MCPG control plane, operated for you. Two command-line tools drive it:

mcpg cloud — the tenant CLI. Log in, publish configs as managed gateways, inspect instances and logs, manage config versions and custom domains.
mcpg admin — the platform-operator CLI, for organization owners who administer the fleet and tenant orgs.

A published config becomes a running gateway (an instance) with its own MCP endpoint URL. Re-publishing the same name updates it in place and records a new config version. Everything you'd configure on a self-hosted gateway — tools, identity, policy, audit — is just the config you publish.

Get started

bash

mcpg cloud login                              # OIDC sign-in
mcpg cloud use --org acme --workspace prod    # set your working context
mcpg config check gw.yaml                      # validate before you ship
mcpg cloud publish edge --config gw.yaml       # publish → managed gateway
mcpg cloud instances                           # endpoint URL + instance id

What you get

Capability	How
Managed gateway	Publish a config → a running MCP endpoint.
Version history	Every publish is a version; diff and roll back.
Your own hostname	Custom domains with DNS ownership proof.
Logs & metrics	`mcpg cloud logs <name> --follow`; fleet metrics roll up in the dashboard.
Org & fleet admin	Tenant administration via `mcpg admin`.

Where to go next

Publish a config — the end-to-end publish flow.
Versions and rollback — manage config history.
Custom domains — serve on your own hostname.
mcpg cloud reference — every command and flag.

To license enterprise (BUSL-1.1) plugins for production, email agent@mcpg.dev or use mcpg.cloud.