Octri

Custom domain

Serve your hosted MCP server from your own address, such as mcp.acme.com, so the URL people connect to carries your name rather than Octri's.

This is separate from your docs domain. You can use either or both.

Setting one up

  1. Add the hostname

    In MCP Studio, under Custom domain, enter the hostname and choose Add domain.

  2. Create the DNS records

    Add both records at your DNS provider: a CNAME that points the hostname at Octri, and a TXT record that proves you own it.

  3. Verify

    Once the records are in place, verify them. Octri issues a certificate, which usually takes a few minutes, and renews it for you.

The page shows the certificate's state: Certificate pending, Certificate live or Certificate failed.

Connecting

Clients then connect at:

text
https://mcp.acme.com/mcp

Tool group and installation addresses move with it.

Sign-in

Sign-in tokens are bound to the address they were issued on, so a token from your domain is not accepted on api.octri.dev, and the other way round. The sign-in pages themselves stay on Octri's address, and name your domain when the sign-in started there.

Removing it

Choose Remove. The custom address stops answering at once, and people signed in through it have to sign in again.

Tell people before you move

A move in either direction changes the address in everyone's client config, and signs them out. Pick the domain early.

From the CLI

You can add, verify and remove the domain with octri mcp domain.