Domains

Every account gets a hub domain: <slug>.finchmcp.com. Services live under it as paths. You can also bring your own hostname and serve the same services on your domain.

Your hub domain

The slug is the routing key. It resolves <slug>.finchmcp.com to your account, and each service answers under its app_path:

https://.finchmcp.com//
# an MCP server answers at //mcp

A slug is assigned automatically the first time you open the dashboard or a box enrolls, so your account always has a working public host. Change it in the dashboard under Settings, in the Hub domain row. Availability is checked live as you type. Slugs are lowercase letters, digits, and hyphens, at least 3 characters.

Custom domains

Serve your boxes on your own domain instead of .finchmcp.com. The recommended naming is one hostname per box, with the service in the path:

https://.yourdomain.com//

Setup is three steps, all in dashboard Settings under Custom domains:

Step	What happens
1. Add the hostname	Name it after the box it reaches, for example `pelican.yourdomain.com`.
2. Create the DNS record	After adding, the dashboard shows the exact CNAME record to create at your DNS provider. It points your hostname at Finch.
3. Wait for DNS	Once the record resolves, the certificate is issued automatically and your services go live on the new name.

Removal is immediate. Removing a hostname stops traffic on it right away. Your hub domain keeps working; custom domains are additional names, not replacements.

From the CLI

Custom hostnames can also be managed with finch domain:

finch domain ls                    # list custom hostnames on this account
finch domain add mcp.example.com   # add one; prints the CNAME to configure
finch domain rm mcp.example.com    # remove one; traffic stops immediately

finch domain ls supports --json for scripting. Removal only works for hostnames on your account; the hub slug itself is changed in the dashboard, not the CLI.

← Access control CLI reference →