Skip to main content
By default, every 0mcp server is available through a hosted 0mcp endpoint. You can also use a custom domain to provide your own branded MCP endpoint, such as mcp.example.com. Using a custom domain gives you a stable endpoint that’s independent of the default 0mcp domain.

​
Connect a custom domain

To configure a custom domain:
  1. Open your server and go to Settings.
  2. Under Custom Domain, enter the hostname you want to use, such as mcp.example.com.
  3. Copy the DNS record generated by 0mcp.
  4. Add the record to your DNS provider.
  5. Wait for domain verification and TLS provisioning to complete.
  6. Once the domain becomes Active, update your MCP client to use the new endpoint.
Do not update production clients until the custom domain shows Active in 0mcp.

​
DNS requirements

When configuring your domain:
  • Enter only the hostname, such as mcp.example.com.
  • Do not include https://, paths, or query parameters.
  • Ensure the DNS record matches the value provided by 0mcp.
  • During verification, keep the record unproxied if instructed by the dashboard.
DNS propagation and certificate issuance may take a few minutes depending on your DNS provider.

​
Best practices

  • Use one hostname for each MCP server.
  • Choose a stable hostname that won’t need to change.
  • Update your client configuration after the domain becomes active.
  • Remove old or conflicting DNS records before reconnecting the same hostname.

​
Troubleshooting

If your domain doesn’t become active:
  • Verify the DNS record exactly matches the value provided by 0mcp.
  • Make sure the hostname isn’t already connected to another server.
  • Confirm you’re using a hostname rather than a full URL.
  • Allow time for DNS propagation and certificate provisioning to complete.
If the domain is active but your client still cannot connect, follow MCP connection issues.