gigamcp/ docs

Custom domain

Run gigamcp on a host you own, e.g. mcp.acme-bank.com. We provision the TLS certificate via AWS ACM and route requests through our shared ALB with host-header matching. No additional infrastructure runs on your side beyond a single CNAME.

Prerequisites

  • A host you control (any subdomain or apex works).
  • Ability to create DNS records (CNAME for subdomains; ALIAS / ANAME for an apex).
  • Workspace admin or owner role inside gigamcp.

Step-by-step

  1. Open Enterprise → Custom domain.
  2. Enter the host you want (e.g. mcp.acme-bank.com) and press Save. The status flips to Pending.
  3. We display two pieces of information:
    • CNAME target — almost always app.gigamcp.io.
    • Verify token — a value of the form gigamcp-domain-verify=….
  4. On your DNS provider (Route53, Cloudflare, etc.) create the CNAME pointing your host at app.gigamcp.io. TTL 300 is fine.
  5. Once DNS resolves, press Verify on the custom-domain page. We:
    1. Resolve the CNAME and confirm it points at our edge.
    2. Fetch http://<your-host>/.well-known/gigamcp-domain-verifyand confirm the body equals the verify token. (The first verification round-trip uses plain HTTP because ACM hasn't issued a cert yet.)
  6. On success the status flips to Verified and we kick off ACM certificate issuance. Within 10 minutes your host serves gigamcp over HTTPS with a valid cert.

Apex domains

CNAMEs at the apex are non-standard. Use Route53 ALIAS, Cloudflare CNAME flattening, or any ANAME equivalent and target app.gigamcp.io.

Trust model

Verification is required to prevent host hijacking — without the well-known challenge anyone could claim a domain they don't own and intercept traffic the moment the victim creates the CNAME. The challenge is a high-entropy random token regenerated each time you save a new host.

Removing a custom domain

Press Remove. Within 60 seconds the host stops resolving on our side; your members go back to app.gigamcp.io/<your-slug>. The ACM cert is revoked asynchronously by AWS.

Caveats

  • We do not yet support multiple custom domains per tenant. If you need this email enterprise@gigamcp.io.
  • The MCP server URL changes from https://app.gigamcp.io/t/<slug>/mcp to https://<your-host>/mcp. Update the URL in Cursor / Claude Desktop / VS Code Continue accordingly.
  • Cookies become first-party on your domain. Members who had active sessions on app.gigamcp.io need to log in again the first time they hit the vanity host.