Custom domains

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.

By default a published gateway answers on a platform-assigned endpoint. To serve it on your own hostname — mcp.acme.com instead of a generated URL — attach a custom domain. Ownership is proven with a DNS record so no one can claim a name they don't control.

1. Add the domain and prove ownership

bash

mcpg cloud domains add mcp.acme.com

This returns a DNS-TXT challenge. Create that TXT record at your DNS provider, then verify:

bash

mcpg cloud domains verify mcp.acme.com
mcpg cloud domains list             # see status of every domain

2. Attach it to an instance

Point a published gateway at the verified hostname with --custom-hostname on publish (re-publishing the same name updates in place):

bash

mcpg cloud publish edge --config gw.yaml --custom-hostname mcp.acme.com

Add a CNAME (or the address record the platform gives you) from mcp.acme.com to the instance's endpoint so client traffic routes to it.

Remove a domain

bash

mcpg cloud domains remove mcp.acme.com

Where to go next

Publish a config — where --custom-hostname is set.
mcpg cloud reference — the full domains command surface.