MCP server · Content and web

DNSimple MCP server

DNSimple in any MCP client, through Memtro: DNSimple does not publish this server. Memtro's DNSimple connector reads DNSimple through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

DNSimple (DNS hosting and domain registrar): domains with state, expiry and auto-renewal, DNS zones and their records, whether a zone has reached every name server, SSL certificates, a domain's name servers, domain availability and email forwards; can create, change and delete DNS records, add and remove email forwards, switch auto-renewal and transfer lock on or off, switch WHOIS privacy off, change a domain's name servers and delete a domain from the account.

Reads

  • dnsimple_list_domainsDomains in the DNSimple account: state (hosted, registered, expired), expiry date, auto-renewal and WHOIS privacy.
  • dnsimple_get_domainOne DNSimple domain with its state, expiry, auto-renewal and WHOIS privacy, and, for a domain registered with DNSimple, its name servers.
  • dnsimple_check_domainWhether a domain name is available to register at DNSimple, and whether it is premium (priced above the standard rate).
  • dnsimple_list_zonesDNS zones hosted in the DNSimple account: whether DNS is active, record counts and the plan's record limit.
  • dnsimple_list_recordsDNS records in a DNSimple zone: name ("@" is the apex), type, content, TTL and priority.
  • dnsimple_check_zone_distributionWhether a DNSimple zone's current records have reached every DNSimple name server, so a change made is being served everywhere.
  • dnsimple_list_certificatesSSL certificates for a DNSimple domain: common name, other names, state, issuer, auto-renewal and expiry.
  • dnsimple_list_email_forwardsEmail forwards on a DNSimple domain: which address forwards to which.

Acts, when you ask

These change something in DNSimple. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • dnsimple_create_recordCreates a DNS record in a DNSimple zone.
  • dnsimple_update_recordChanges a DNS record in a DNSimple zone (name, content, TTL, priority or regions; the type cannot change).
  • dnsimple_delete_recordPermanently deletes a DNS record from a DNSimple zone; the name stops resolving to it within moments.
  • dnsimple_create_email_forwardCreates an email forward on a DNSimple domain, so mail to alias@domain is delivered to the destination address.
  • dnsimple_delete_email_forwardPermanently deletes an email forward on a DNSimple domain; mail to that alias stops being delivered.
  • dnsimple_set_auto_renewalSwitches auto-renewal on or off for a domain registered with DNSimple.
  • dnsimple_set_transfer_lockLocks or unlocks a domain registered with DNSimple against transfer to another registrar.
  • dnsimple_disable_whois_privacySwitches WHOIS privacy off for a domain registered with DNSimple, so the registrant's name, address, email and phone are published in public WHOIS.
  • dnsimple_set_name_serversReplaces the name servers of a domain registered with DNSimple.
  • dnsimple_delete_domainPermanently deletes a domain and its zone from the DNSimple account; its DNS records stop being served.

Connect it

First connect DNSimple on Dashboard → Connections, then add Memtro to your client once. The DNSimple tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared DNSimple connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which domains expire in the next 60 days?
  • › What MX records does acme.com have?
  • › Has yesterday's change to the www record reached every name server?
  • › Is acme.io available to register?
  • › Point staging.acme.com at the new load balancer with a CNAME.

Questions

Is this an official DNSimple MCP server?
No. It is Memtro's MCP server with Memtro's DNSimple connector behind it: the connector reads DNSimple through its API with the credentials you connect on Dashboard → Connections, and DNSimple publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in DNSimple?
Only when you ask, and only what it has been granted: create a DNS record (live straight away); change a DNS record; delete a DNS record (permanent); create an email forward; delete an email forward (permanent); switch a domain's auto-renewal on (future renewals are charged) or off; lock a domain against transfer, or unlock it; switch a domain's WHOIS privacy off (publishes the registrant's contact); change a domain's name servers; delete a domain from the account (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Content and web

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time