Domainee MCP MCP server

An official MCP server provided by Domainee that allows AI agents to manage custom domains, SSL certificates, and DNS records for SaaS applications. It exposes tools for listing, creating, updating, and deleting domains, as well as checking DNS records and managing webhook endpoints, all authenticated via the user's existing API key.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Domainee

MCP endpoint (Streamable HTTP)

https://mcp.domainee.dev/mcp

Vendor documentation

What you can do with it

List domains with specific status filters
Create and configure customer hostnames
Check DNS and SSL record validity
Manage webhook endpoints for events

Tools advertised by the last live check:

tools_ssl_check
tools_dns_provider_lookup
tools_domain_connect_checker
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_domain_age_checker
tools_subdomain_finder
tools_reverse_ip_lookup
tools_dmarc_record_checker
tools_txt_record_lookup
tools_website_status_checker
tools_dkim_record_checker
tools_domain_availability_checker

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http domainee-mcp https://mcp.domainee.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add domainee-mcp --url https://mcp.domainee.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable domainee-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "domainee-mcp": {
      "url": "https://mcp.domainee.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "domainee-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.domainee.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start domainee-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "domainee-mcp": {
      "type": "http",
      "url": "https://mcp.domainee.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http domainee-mcp https://mcp.domainee.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "domainee-mcp": {
      "url": "https://mcp.domainee.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "domainee-mcp": {
      "serverUrl": "https://mcp.domainee.dev/mcp"
    }
  }
}

See all 148

Do you run Domainee MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing