Skip to main content
Gcore MCP Server provides approximately 30 tools for managing DNS zones and records through natural language. Configuration and client setup are covered in the Gcore MCP Server overview.

​
Configure for DNS

The GCORE_TOOLS environment variable controls which tools are exposed. Setting GCORE_TOOLS="dns.*" loads all DNS tools. 
GCORE_TOOLS="dns.*"
DNS tools follow the dns.<resource>.<operation> naming pattern. The zones tools handle DNS zone management with list, create, get, update, and delete operations. The zones.records tools manage DNS records within zones. The locations tools list DNS server locations, while metrics and lookup tools provide DNS query analytics and record lookups.

​
DNS operations

Natural language requests trigger the corresponding API operations. Listing zones requires no parameters—a request like “List all my DNS zones” returns zone names, record counts, and status. Zone creation requires the domain name. Requesting “Create a DNS zone for newdomain.com” provisions the zone and returns nameserver assignments (such as ns1.gcorelabs.net and ns2.gcdn.services) that must be configured at the domain registrar. Record listing shows all records in a zone. A request to “Show all DNS records for example.com” returns a table with record types, names, values, and TTL settings. Record creation requires the zone name, record type, name, and value. Creating an A record with “Add an A record for api.example.com pointing to 198.51.100.20 with TTL 300” adds the record to the zone. CNAME records use the same pattern—“Add a CNAME record for www.example.com pointing to example.com” creates the alias. MX records require priority—“Add an MX record for example.com with priority 10 pointing to mail.example.com” sets the mail exchanger. TXT records for email authentication use quoted values—“Add a TXT record for _dmarc.example.com with value ‘v=DMARC1; p=reject; rua=mailto:dmarc@example.com’” creates the DMARC policy record. Record updates modify existing entries. A request to “Change the TTL of all A records in example.com to 600 seconds” bulk-updates TTL values. Updating specific records with “Update the A record for api.example.com to point to 198.51.100.25” changes the target address. Record deletion removes entries from the zone. “Delete the CNAME record for old.example.com” removes the specified record. DNS lookups verify record resolution. “Lookup the A record for www.example.com” queries the DNS system and returns the resolved value, TTL, and response time.

​
Multi-step workflows

Complex DNS configurations involve multiple tools executed in sequence. Setting up a new domain requires creating the zone, adding A records for the apex and www subdomain, configuring MX records for email, and adding SPF TXT records for email authentication. A combined request like “Set up DNS for mynewsite.com with A records for @ and www pointing to 198.51.100.50, MX record pointing to mail.mynewsite.com with priority 10, and SPF TXT record” triggers the appropriate tool sequence. Email DNS configuration combines multiple record types. Requesting “Set up email DNS records for example.com with MX record pointing to mail.example.com, SPF record allowing mail.example.com, DKIM record with selector ‘default’, and DMARC record with reject policy” creates the complete email authentication stack. Migration workflows analyze existing zones. “List all records from oldsite.com that I need to recreate in newsite.com” exports records for migration planning. Propagation verification checks DNS resolution. “Check if the A record for api.example.com has propagated” queries multiple DNS servers to confirm record availability.

​
Tool naming patterns

DNS tool names follow the dns.<resource>.<operation> pattern. The dns.zones.list tool lists all DNS zones in the account without parameters and returns zone names, record counts, and status. The dns.zones.create tool requires name (the zone name such as example.com). The dns.zones.records.create tool requires zone_name (the parent zone), name (the record name, using @ for apex), type (A, AAAA, CNAME, MX, TXT, or other record types), and content (the record value), with optional ttl in seconds defaulting to 300.
InfoTool parameters and behavior reflect the Gcore DNS API. Record management is documented in the DNS records guide. Tool filtering options are available in the GCORE_TOOLS reference.