Serve your MCP server from your own domain

How it works

1. On the server’s Deployments tab, open the Custom domain card and add your hostname (subdomains only — e.g. mcp.acme.com, not acme.com).
2. The card generates your records: a CNAME that routes traffic to MCPCloud and a TXT that proves you own the domain.
3. Create both at your DNS provider, then hit Recheck (or wait — verification also runs automatically).
4. Once the certificate is issued the domain flips to Active and your server answers at https://your-host/mcp.

Verify once, use everywhere

Running several servers under one domain — like forge.mcp.acme.com and slate.mcp.acme.com? Verify the parent domain once as a domain namespace (Settings → Domains) and skip per-hostname DNS entirely:

1. Add mcp.acme.com as a namespace and create two records at your DNS provider: one ownership TXT and one wildcard CNAME (*.mcp.acme.com).
2. From then on, attaching anything.mcp.acme.com to a server is a single click — no new DNS records, verification and the certificate complete automatically within minutes.

A namespace also reserves the whole subtree for your workspace, and counts as a single domain toward your plan limit — subdomains under it are free.

Guides by DNS provider

Using a different provider? The records are standard — any DNS host works. The provider pages above cover the two details that vary: where the record editor lives and how the Name field is formatted.