Cnamio
Server Details
Connect your users' custom domains: detect the DNS provider, create records, confirm propagation.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 7 tools
Each tool targets a distinct step: inspect (check_domain), act (connect_domain / connect_domain_automatic), poll (get_connection_status), force refresh (recheck_propagation), plus list and docs. The only near-overlaps are the manual vs automatic connect pair and status vs recheck, but the descriptions explicitly delimit them (api_token precondition, 5-minute throttle, 'follow with get_connection_status').
Every name is snake_case and verb-first (check_, connect_, get_, list_, recheck_), so the pattern is predictable. connect_domain_automatic appends a qualifier rather than using a distinct verb, a minor deviation but still readable and self-explanatory.
Seven tools is well-scoped for a domain-connection service: inspect, two connect paths, status, recheck, list, and integration docs. No tool looks redundant or missing from the workflow.
The setup-to-verified lifecycle is covered (check, connect, status, recheck, list, guide), but there is no disconnect/remove operation, so a connection created via connect_domain has no tool-level teardown. Reading a single connection's details beyond status is also implicit only.
Available Tools
7 toolscheck_domainCheck a domainBRead-onlyInspect
Read-only. Finds where a domain's DNS is hosted and how it can be connected: provider, setupType, connectMethods (api_token when the records can be created with the user's provider token), nameservers, recordState for a single CNAME, and conflicts with records already published.
Inputs: domain (required), dnsRecords (required), checkConflicts.
connect_domainConnect a domain (manual records)AInspect
Starts a manual connection: returns the exact records the domain owner must create at their DNS provider and starts watching propagation on the authoritative nameservers (up to 72 hours). Does not change DNS. Follow it with get_connection_status.
Inputs: domain (required), dnsRecords (required), userId.
connect_domain_automaticConnect a domain with the provider tokenAInspect
Creates the records at the domain's DNS provider with an API token the domain owner provides (only when check_domain returned connectMethods containing api_token). The token is used during this call only and is never stored; existing records are never changed or deleted (a conflict returns 409 with the reasons). Never ask for or use DNS provider passwords.
Inputs: domain (required), dnsRecords (required), providerToken (required), userId.
get_connection_statusConnection statusARead-onlyInspect
Status of a connection: pending, in_progress, completed (connected) or failed (72 hours without propagation).
Inputs: jobId (required).
get_integration_guideCnamio integration guideARead-onlyInspect
Returns the step-by-step guide to add custom domain connection to a project with Cnamio: records, environment variables, server session route, browser connect window, headless API and webhook verification (Node.js and Python). Start here when integrating Cnamio into code.
Inputs: no named parameters.
list_connectionsList connectionsARead-onlyInspect
Recent connections of the application, newest first, optionally for one domain or status. Needs the application credentials (not a session token).
Inputs: limit, domain, status.
recheck_propagationCheck propagation nowBIdempotentInspect
Asks Cnamio to check the domain's authoritative nameservers again now (at most once every 5 minutes per connection).
Inputs: jobId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Connect custom domains via AI agents: DNS pre-flight checks, hand-off connect sessions and checks.
Custom domains API for SaaS: connect, verify, and manage customer domains, SSL, and DNS
Add custom domains with automatic SSL for your SaaS customers, check DNS and see traffic.
Add, check, diagnose and remove your SaaS customers' custom domains from any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search for, purchase, connect, and verify custom domains end to end, including setting up email records, configuring forwarding, diagnosing drift, and confirming TLS issuance without handling DNS records directly. It offers twelve hosted tools covering domain availability, registration orders, provider discovery, and account-wide connection inventory.1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to check domain availability, purchase domains via Stripe, and perform full DNS and nameserver management. It facilitates automated domain lifecycle tasks like record updates and transfer locks without requiring CAPTCHAs.MIT
- AlicenseBqualityCmaintenanceEnables users to inspect and manage domains, DNS records (including A, AAAA, CNAME, MX, TXT and more), HTTP forwards, invoices and dynamic DNS through a hosting provider's API, with previewed change plans, conflict detection, backups and independent readback before writes. Offers DNS shortcuts such as website setup, verification records, bulk IP replacement, zone import/export and backup restore, exposed via local stdio or authenticated Streamable HTTP for a central gateway.27MIT
- AlicenseAqualityCmaintenanceEnables checking domain availability through authoritative registry queries and resolving live DNS records such as A, NS, MX, and TXT for any domain.210 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.