Domainee
About
Custom domains API for SaaS as MCP tools: connect, verify, and manage customer domains, SSL, and DNS from any MCP client. 50 domains free.
Details
- Author
- commonninja
- Categories
- Cloud Service, Infrastructure
Jump to
Setup
Install Domainee in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/commonninja/domainee-mcp-server
Follow the installation instructions in the repository README, then restart your MCP client.
Custom domains API for SaaS, exposed as Model Context Protocol tools. Connect, verify, and manageyour 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, statelessModel Context Protocolserver 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.
Most domain MCP servers wrap a registrar's API so an agent can managedomains you own— search, buy, renew, edit nameservers at GoDaddy / Namecheap / Dynadot / NameSilo.
Domainee solves the other problem: lettingyour customers point their own domains at your app. You're a SaaS, your customer ownsshop.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.
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 athttps://domainee.dev/developers) unlocks the 11 workspace tools; calling one without a key returns401plus aWWW-Authenticateheader 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).
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 atext/event-streamresponse:
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
27 tools in two tiers. The16 free diagnostic tools need no key; the11 workspace tools require a Bearerand are only registered when a token is present, so an unauthenticatedtools/listreturns 16 and an authenticated one returns 27.
Workspace tools (11 — Bearer API key required)
typeacceptsa,aaaa,cname,mx,txt,ns,caa. Comparison is case-insensitive and trailing dots are stripped. Webhook events aredomain.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 athttps://api.domainee.dev/v1/tools/<name>— seehttps://domainee.dev/free-apis.
Onboard a customer domain."Connectshop.acme.comtohttps://acme.myapp.com." The agent callscreate_domain, reads the returned CNAME target out ofdnsRecords, and tells the customer exactly what to publish. Once they say they've done it, it callscheck_domainto verify immediately rather than waiting for the monitor.
Debug a broken domain."Why isshop.acme.comshowing a certificate error?" The agent callsget_domainfor our view of the status, thentools_cname_lookupandtools_ssl_checkfor 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_domainswithstatus: "failed", thendns_check_records_existacross the results in one batched call of up to 50 records.
Free tier: 50 custom domains + 100 GB bandwidth/month, no credit card. Usage pricing beyond that athttps://domainee.dev/pricing. The 16 diagnostic tools are free and keyless regardless.
- MCP Registry —dev.domainee/domaineeonhttps://registry.modelcontextprotocol.io
- Glama —https://glama.ai/mcp/connectors/dev.domainee/domainee
- Smithery —https://smithery.ai/server/admin-cl6n/domainee
- Claude connector directory — listed as a community connector; find it in Claude under Settings → Connectors
- Product:https://domainee.dev
- MCP docs:https://domainee.dev/mcp·https://domainee.dev/docs/mcp
- API docs:https://domainee.dev/docs
- Free keyless APIs:https://domainee.dev/free-apis
- For agents:https://domainee.dev/llms.txt·https://domainee.dev/llms-full.txt
Discovery and documentation only — the server is hosted, so there is nothing to clone or run. It holds theserver.jsonthat the MCP Registry reads and this README. The implementation lives in the Domainee monorepo.
Navigate your Aiven projects and interact with the PostgreSQL®, Apache Kafka®, ClickHouse® and OpenSearch® services
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform.
Get prescriptive CDK advice, explain CDK Nag rules, check suppressions, generate Bedrock Agent schemas, and discover AWS Solutions Constructs patterns.
This AWS Labs Model Context Protocol (MCP) server for CloudTrail enables your AI agents to query AWS account activity for security investigations, compliance auditing, and operational troubleshooting.
Core AWS MCP server providing prompt understanding and server management capabilities.
Analyze CDK projects to identify AWS services used and get pricing information from AWS pricing webpages and API.
Query and analyze your Axiom logs, traces, and all other event data in natural language
Manage and interact with Microsoft Azure services.
Bastion: External Attack Surface Monitoring
Ask your AI assistant about your attack surface: run scans, catch expiring certificates and domains, triage findings, and generate reports.
Agent-ready global image CDN that AI agents can install and operate through MCP.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.

