Host your MCP server on your own custom domain

A shared MCP URL works perfectly well, but serving your server from mcp.yourdomain.com makes it feel like a native part of your product — better for branding, trust, and customer-facing docs. This guide walks through putting your MCP server on a custom domain: the DNS records you add, how certificate validation works, and the verification flow end to end.

Why use a custom domain

The endpoint is what your customers paste into their AI client and what you publish in your docs. A branded host signals that the integration is official and yours. It also decouples your public endpoint from the underlying infrastructure — you can change what's behind it without customers ever updating their config.

Step 1: Add your domain in Cast

In your workspace, open the domain settings and enter the hostname you want, such as mcp.yourdomain.com. Cast generates the exact DNS records you need to add at your DNS provider.

Step 2: Add three DNS records

At your DNS provider (Cloudflare, Route 53, Namecheap, etc.), add the records Cast shows you. There are three, each with a distinct job:

Step 3: Verify

Back in Cast, click Verify. Cast checks that the records resolve, confirms domain ownership, waits for the certificate to be issued and validated, then attaches the certificate and a routing rule so requests to your hostname reach your workspace. When it's done, the domain shows as verified.

If verification doesn't pass immediately

• Give DNS time — propagation can take minutes to hours depending on your provider and TTL.
• Check for typos — a single wrong character in a record value will fail validation.
• Disable proxying — set records to DNS-only if your provider proxies by default.
• Re-run verify — it's safe to retry; Cast re-checks the current state each time.

Step 4: Use the branded URL

Once verified, your MCP endpoint is available at your custom host over HTTPS. Update your connect snippets and docs to use it. Customers connecting through the branded URL get the same server — now under your name.

See where your customers connect from

Once a branded endpoint is live and customers start connecting, Cast tracks each connection as a session and resolves its geography from the client IP. That turns your custom domain into a live map of demand — which regions use your server, how long sessions last, and how many tools each one calls:

Pair this with the session-pattern view (covered in our analytics guide) and your branded server becomes a feedback loop: you see who connects, what they do, and which tools to add next — all under your own domain.

Frequently asked questions