Skip to main content
Glama

Cnamio

Server Details

Connect your users' custom domains: detect the DNS provider, create records, confirm propagation.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

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').

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness3/5

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 tools
check_domainCheck a domainB
Read-only
Inspect

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 statusA
Read-only
Inspect

Status of a connection: pending, in_progress, completed (connected) or failed (72 hours without propagation).

Inputs: jobId (required).

get_integration_guideCnamio integration guideA
Read-only
Inspect

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 connectionsA
Read-only
Inspect

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 nowB
Idempotent
Inspect

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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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
    • A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      27
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources