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/configs builds an MCPG gateway config from the plugin catalog, checks it as you type, and encrypts it in your browser before anything is uploaded. You get a URL and a secret; the service stores ciphertext and never holds the key.

Turn a validated gateway config into a running managed MCP endpoint on mcpg.cloud — log in, set your context, validate, publish, and read back the endpoint URL. Re-publishing the same name updates in place.

Give a managed gateway the API tokens, keys, and passwords its config must not carry. Register a value per gateway with mcpg cloud secret set, reference it as ${secret.NAME}, and rotate it with one command — no publish, no restart, and the platform never shows a value back.

Every publish to mcpg.cloud is a numbered config version. How to list history, diff any two versions, and roll a managed gateway back to a known-good one.

Serve a managed mcpg.cloud gateway on your own hostname. Prove ownership with a DNS-TXT record, attach the domain at publish time, and manage the domain list from the CLI.

The platform-operator side of mcpg.cloud — seed and manage tenant organizations, and register or decommission the clusters that host gateways, with the mcpg admin CLI.

The managed MCPG relay — get a public MCP URL for a gateway that binds no port, or federate a gateway running in your own infrastructure so its secrets never reach the cloud. Plans, concurrent-tunnel quota, and byte-based overage.

Choose where a published gateway runs, what a region choice commits to, why an instance stays where it was placed, and how to move one when you need to.