Domainee MCP Server

> Custom domains API for SaaS, exposed as Model Context Protocol tools. Connect,

> verify, and manage your customers' domains, SSL, and DNS from any MCP client.

> 50 domains free.

Domainee is a custom domains API for SaaS with a native MCP server — 50 domains and

100 GB free. This is the hosted, stateless Model Context Protocol

server that lets AI agents (Claude, Cursor, Windsurf, and any MCP-aware client) drive

the Domainee API directly: onboard a customer's hostname and get back the CNAME target,

force DNS and SSL probes, debug "my domain isn't working" tickets, and manage webhook

endpoints. Same Bearer key, rate limits, and workspace as the REST API. Nothing to deploy.

This is not a registrar MCP server

Most domain MCP servers wrap a registrar's API so an agent can manage **domains you

own** — search, buy, renew, edit nameservers at GoDaddy / Namecheap / Dynadot / NameSilo.

Domainee solves the other problem: letting **your customers point their own domains at

your app**. You're a SaaS, your customer owns `shop.acme.com`, and you need it serving

their storefront over HTTPS in a minute without them touching your infrastructure. That

means custom-hostname routing, automatic certificate issuance and renewal, DNS

verification, and a webhook when it goes live — the "Cloudflare for SaaS" shape, not the

registrar shape.

If you want an agent to buy you a domain, use a registrar server. If you want an agent

to onboard a customer's domain into your product, this is the one.

Endpoint

https://mcp.domainee.dev/mcp

Remote, streamable HTTP, stateless. No install, no local process, nothing to deploy.

Auth is optional for discovery. `initialize`, `tools/list`, and all 16 free

diagnostic tools answer anonymously. A Domainee API key (`sk_live_…`, minted at

) unlocks the 11 workspace tools; calling one without a

key returns `401` plus a `WWW-Authenticate` header pointing at our OAuth metadata, which

is what starts the OAuth flow in MCP clients. OAuth is also supported end to end

(RFC 9728 protected-resource metadata + RFC 8414 authorization-server metadata).

Install

Claude Code / CLI:

claude mcp add --transport http domainee https://mcp.domainee.dev/mcp \
  --header "Authorization: Bearer sk_live_YOUR_KEY"

Claude Desktop / Cursor / Windsurf (any HTTP-transport client):

{
  "mcpServers": {
    "domainee": {
      "url": "https://mcp.domainee.dev/mcp",
      "headers": { "Authorization": "Bearer sk_live_YOUR_KEY" }
    }
  }
}

Try it with no key at all — this returns the 16 free tools as a `text/event-stream`

response:

curl -s https://mcp.domainee.dev/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
  | grep '^data: ' | sed 's/^data: //' | jq '.result.tools | length'
# 16

Tools

27 tools in two tiers. The 16 free diagnostic tools need no key; the **11 workspace

tools require a Bearer** and are only registered when a token is present, so an

unauthenticated `tools/list` returns 16 and an authenticated one returns 27.

Workspace tools (11 — Bearer API key required)

`type` accepts `a`, `aaaa`, `cname`, `mx`, `txt`, `ns`, `caa`. Comparison is

case-insensitive and trailing dots are stripped. Webhook events are

`domain.created`, `domain.verified`, `domain.failed`, `domain.expired`,

`domain.deleted`, `domain.monitor_updated`.

Free diagnostic tools (16 — no key, no signup)

Read-only SSL / DNS / WHOIS lookups, usable by any agent against any domain:

`tools_ssl_check`, `tools_dns_record_lookup`, `tools_whois_lookup`,

`tools_cname_lookup`, `tools_http_header_checker`, `tools_dns_propagation_checker`,

`tools_redirect_checker`, `tools_spf_record_checker`, `tools_dkim_record_checker`,

`tools_dmarc_record_checker`, `tools_txt_record_lookup`, `tools_domain_age_checker`,

`tools_domain_availability_checker`, `tools_subdomain_finder`,

`tools_reverse_ip_lookup`, `tools_website_status_checker`.

The same 16 are available as keyless REST endpoints at

`https://api.domainee.dev/v1/tools/` — see .

What agents do with it

Onboard a customer domain. "Connect `shop.acme.com` to `https://acme.myapp.com`."

The agent calls `create_domain`, reads the returned CNAME target out of `dnsRecords`,

and tells the customer exactly what to publish. Once they say they've done it, it calls

`check_domain` to verify immediately rather than waiting for the monitor.

Debug a broken domain. "Why is `shop.acme.com` showing a certificate error?" The

agent calls `get_domain` for our view of the status, then `tools_cname_lookup` and

`tools_ssl_check` for ground truth from public DNS, and can tell the difference between

"the customer never published the record", "it's published but not propagated yet", and

"there's a CAA record blocking issuance".

Audit the fleet. "Which customer domains are failing?" — `list_domains` with

`status: "failed"`, then `dns_check_records_exist` across the results in one batched

call of up to 50 records.

Pricing

Free tier: 50 custom domains + 100 GB bandwidth/month, no credit card. Usage pricing

beyond that at . The 16 diagnostic tools are free and

keyless regardless.

Listings

• MCP Registry — `dev.domainee/domainee` on
• Glama —
• Smithery —
• Claude connector directory — listed as a community connector; find it in Claude under

Settings → Connectors

Links

• Product:
• MCP docs: ·
• API docs:
• Free keyless APIs:
• For agents: ·

About this repo

Discovery and documentation only — the server is hosted, so there is nothing to clone

or run. It holds the `server.json` that the MCP Registry reads and this README. The

implementation lives in the Domainee monorepo.

Issues and questions are welcome here.

License

MIT — see LICENSE.