DNSCove

DNSCove docs

Updated

MCP server

DNSCove ships a Model Context Protocol server, so an AI assistant can read and configure a tenant's DNS directly. It is the same capability as the JSON API, replayed against the same handlers and the same dnsc_ machine tokens.

https://api.dnscove.com/mcp

Connect

Claude Code (HTTP)

claude mcp add --transport http dnscove https://api.dnscove.com/mcp \
  --header "Authorization: Bearer dnsc_..."

Any Streamable HTTP client

{
  "mcpServers": {
    "dnscove": {
      "type": "http",
      "url": "https://api.dnscove.com/mcp",
      "headers": { "Authorization": "Bearer dnsc_..." }
    }
  }
}

stdio-only clients

The bridge is published as @dnscove/mcp. It carries the same token and scope rules as the HTTP transport:

{
  "mcpServers": {
    "dnscove": {
      "command": "npx",
      "args": ["-y", "@dnscove/mcp"],
      "env": { "DNSCOVE_API_TOKEN": "dnsc_..." }
    }
  }
}

Create a machine token in the console under Settings → API keys. A tenant-admin token can act on any zone in the tenant and is root-equivalent for DNS; a zone-admin token is pinned to one zone and is the right choice for an agent that manages a single domain. acme-dns01 tokens are refused by the MCP endpoint.

Tools

Sixteen tools, each mapping onto one JSON API operation.

Tool Does Scope Confirm
list_zones Every zone in the tenant, with status and serials. tenant-admin no
get_zone One zone's settings and publish state. both no
create_zone Create a PENDING_VERIFICATION zone and return the challenge TXT. Does not publish. tenant-admin no
update_zone Change negative_ttl and publish. both no
list_rrsets Every record set in a zone. both no
upsert_rrset Create or replace a whole (name, type) set and publish. CREATE refuses an existing set; UPSERT replaces it. both no
delete_rrset Delete a whole (name, type) set and publish. both yes
get_delegation Read the parent delegation and whether the NS point at DNSCove. both no
verify_zone Verify the _dnscove-challenge TXT and activate a pending zone. The handler publishes on activation. both no
get_parity Compare stored records with live DNS after a migration. both no
get_dnssec Read DNSSEC signing state. Enabling and disabling stay console actions. both no
publish Publish saved changes to the edge. both no
import_route53 Import an aws route53 list-resource-record-sets export as a pending zone. Does not publish. tenant-admin yes
delete_pending_zone Delete a pending zone and its records after a failed import. Refuses active zones. tenant-admin yes
solve_acme_challenge Add or remove one _acme-challenge TXT value. The handler publishes; MCP does not publish again. both yes
get_billing Read plan, zone usage, and subscription state. Billing writes are not exposed. tenant-admin no

Every tool reports its required scope and whether it is read-only or destructive, so a client can prompt before a write.

Safety

Availability

The first release is enabled for the anchor tenant. External-tenant access waits on per-tenant published-state snapshots: the edge snapshot is fleet-wide, so a publish that includes another tenant's staged zone would cross the tenant boundary. Until that work ships, do not issue an MCP token to an external tenant.

See also