Domains

Every account gets an address on finchmcp.com, and every service you publish lives under it as a path. Custom domains are on the way but don't serve traffic yet.

Your account address

Your account address (also called the slug) is the first part of every URL finch gives you. finch picks it the first time you use your account: a word, a bird and a number, such as sunny-wren-42. Each service answers under its name:

https://<slug>.finchmcp.com/<name>/
# an MCP server answers at /<name>/mcp

https://sunny-wren-42.finchmcp.com/notes/mcp

The address stays the same across restarts, reboots and network changes, and for every machine that serves your services. There is no command to rename it yet. finch add prints each service's full URL, and finch fleet lists them all (the url field with --json).

A mistyped address gets a 404 that says no finch account uses it, so check the URL against finch fleet.

Custom domains Not live yet

Custom domains don't serve traffic yet. The finch domain commands below accept and list hostnames, but the part of finch that routes a custom hostname to your services isn't switched on. Use your <slug>.finchmcp.com address for now. This page will say when that changes.

When they are live, you'll be able to serve your services on your own hostname, one per machine, with the service in the path:

https://<machine>.yourdomain.com/<name>/

The commands that exist today:

finch domain ls                    # list custom hostnames on this account
finch domain add mcp.example.com   # record one and print the DNS record it will need
finch domain rm mcp.example.com    # remove one

finch domain ls takes --json. Removal only works for hostnames on your account. Your finchmcp.com address keeps working either way; a custom domain would be an extra name, not a replacement.

← Access control CLI reference →