mocop
Browse · Docs · Guide · Analyze

Cnamio

MCP server by Cnamio · mcp

Cnamio connects end users' custom domains to an app: it finds the DNS provider, creates the records with a provider token or returns the exact records to copy, confirms propagation and sends a signed webhook. Happy path from zero, in one session: (1) when adding custom domains to a codebase, start with get_integration_guide and follow it in the codebase (server SDK: npm i cnamio or pip install cnamio). (2) No credentials yet? start_sandbox returns a sandbox session: pass its auth_token as sandboxToken to check_domain, connect_domain, connect_domain_automatic, get_connection_status and recheck_propagation to run the flow end to end with any domain (nothing real is touched), to build and test before the developer has credentials. (3) Ask the developer for their email and their agreement to https://cnamio.com/terms and https://cnamio.com/privacy, then call start_signup with consent: true (only after they agreed): they get a verification link; opening it and accepting the Terms and Privac…

Endpoint: https://api.cnamio.com/mcp

Verification: observed. Source: crawl.

Capabilities (11)

  • get_integration_guide
  • start_sandbox
  • start_signup
  • check_domain
  • connect_domain
  • connect_domain_automatic
  • get_connection_status
  • recheck_propagation
  • list_connections
  • create_share_link
  • revoke_share_link
About · Contact · Privacy