Cloud DNS MCP. Manage global DNS records via conversation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Cloud DNS (Anycast DNS Provider API) MCP Server manages your global DNS records directly from your AI agent. List zones, create, delete, and update A, CNAME, and MX records across your entire infrastructure via natural language.
It gives your agent full CRUD control over your Anycast DNS settings.
What your AI agents can do
Create record
Adds a brand new DNS record of any type (A, CNAME, MX, etc.) to a specified zone.
Create zone
Establishes an entirely new DNS zone for a domain name.
Delete record
Removes a specific DNS record from a zone.
List all existing DNS zones, or create and delete new ones for your domain infrastructure.
Create, read, update, or delete specific record types (A, CNAME, MX, TXT, etc.) within any target zone.
Fetch a complete list of all records for a specified zone to check its current state.
Modify existing records, including changing Time-To-Live (TTL) values or adjusting MX record priorities.
Use natural language commands to execute complex DNS changes, bypassing manual dashboard navigation.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Cloud DNS (Anycast DNS Provider API) MCP Server: 7 Tools for DNS Management
Use these seven tools to programmatically manage the full lifecycle of your DNS records and zones via your AI agent.
019e5d08create record
Adds a brand new DNS record of any type (A, CNAME, MX, etc.) to a specified zone.
019e5d08create zone
Establishes an entirely new DNS zone for a domain name.
019e5d08delete record
Removes a specific DNS record from a zone.
019e5d08delete zone
Deletes an entire DNS zone.
019e5d08list records
Retrieves a complete list of all records currently configured within a specific zone.
019e5d08list zones
Shows all DNS zones that are currently managed under the account.
019e5d08update record
Modifies the value, TTL, or priority of an existing DNS record.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Cloud DNS (Anycast DNS Provider API), then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
The Cloud DNS MCP Server gives your AI agent full control over your global DNS records. You can list all existing zones, or create and delete new ones for your domain infrastructure. You've got full CRUD power over your Anycast DNS settings.
To manage records, your agent can create a record—adding any type (A, CNAME, MX, etc.) to a specified zone. It can delete a record by removing a specific entry from a zone. It also updates a record, letting you modify the value, TTL, or priority of an existing entry.
Want to see what's running? You can list all records in a zone to pull up a complete rundown of everything configured. You can also list all zones to show every DNS zone managed under your account.
Need to set up a new domain? You can create a zone to establish an entirely new DNS zone for a domain name. You can also delete a zone to take out an entire DNS zone.
Your agent executes these changes using natural language, letting you bypass clicking around in a dashboard.
How Cloud DNS MCP Works
- 1 Subscribe to the server and input your Cloud DNS API Key.
- 2 Tell your AI agent what you need: e.g., 'Create an A record for api.example.com pointing to 203.0.113.5.'
- 3 The agent calls the appropriate tool, executes the change against Cloud DNS, and reports the result.
The bottom line is that your agent handles all the API calls, so you just talk to it.
Who Is Cloud DNS MCP For?
The DevOps engineer who needs to automate DNS record provisioning during a CI/CD pipeline. The system administrator who manages global Anycast zones via simple text commands. The developer who needs to quickly point subdomains or verify domains without leaving their IDE.
Uses the agent to programmatically create or delete DNS records as part of deployment workflows.
Manages global zone definitions and records across multiple locations using natural language commands.
Runs the agent from their IDE to quickly update TXT records for domain verification or point subdomains to new services.
What Changes When You Connect
- Forget clicking through 15 dashboard menus. You tell your agent to run
create_record, and the change hits the global DNS layer instantly. This is direct command execution, not form filling. - Need to audit a complex setup? Use
list_recordsto pull every record for a zone. You get a full inventory in seconds, perfect for troubleshooting resolution issues. - Updating records used to be a pain. Now, with
update_record, you can change a TXT record's TTL or an MX record's priority just by telling your agent. No manual adjustments needed. - Setting up new services is faster.
create_zonelets you build out an entirely new domain structure, whilecreate_recordpoints the necessary records in minutes. - The agent handles the complexity. You don't need to remember API parameters; you just ask for the outcome. This works across all record types (A, CNAME, MX, etc.).
- Full visibility into your infrastructure.
list_zonesshows you every managed domain, giving you a clear map of your current digital assets.
Real-World Use Cases
New subdomain deployment
The dev team needs to point api.staging.com to a new load balancer IP. They tell their agent: 'Create an A record for api.staging.com pointing to 192.0.2.1.' The agent uses create_record, and the record is live immediately.
Decommissioning a service
A service is shut down, and its DNS records need to be removed. The sysadmin asks the agent to run delete_record for all associated records in the target zone. The agent cleans up the records, preventing orphaned entries.
Auditing domain changes
The compliance team needs to verify that the billing.corp.net zone only has records pointing to approved services. They ask the agent to run list_records on that zone, getting a full, verifiable dump of every entry.
Migrating a service's domain
The team moves a service from old.corp.net to new.corp.net. They ask the agent to create_zone for the new domain, and then use update_record to point the primary records over, managing the transition entirely via text.
The Tradeoffs
Manual Dashboard Work
Logging into the DNS console, navigating to the zone, selecting the record, clicking 'Edit', typing the IP, and saving. This is slow, error-prone, and requires context switching.
→
Tell your agent to update_record. It handles the entire workflow—selecting the zone, updating the field, and saving—with a single command.
Guessing Record Types
Trying to remember if a specific service uses an A record or a CNAME record, leading to incorrect configuration attempts and service downtime.
→
Use your agent to list_records first. It pulls the full configuration list, showing you the exact record type and value you need to manage.
Partial Deletion
Manually deleting only the primary record, but forgetting the associated TXT records, which leaves the domain unresolved and fails verification checks.
→
Use delete_record and prompt the agent to find all associated records for the given service before deleting them. This ensures a clean, complete removal.
When It Fits, When It Doesn't
Use this server if your workflow requires managing the lifecycle of domain records (A, MX, CNAME, etc.) and you need to execute those changes from a chat or IDE. You need the ability to talk to your infrastructure. Don't use this if you only need to view records without making changes; you'd use a simple read-only API. Don't use this if you manage records through a different system (like AWS Route 53 or Cloudflare DNS); use those alternatives instead. If you need to manage other infrastructure—like load balancers or firewalls—this server won't help.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Cloud DNS. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 7 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Updating DNS records shouldn't require navigating three different web dashboards.
Today, updating a single subdomain record means logging into the DNS provider, finding the correct zone, locating the specific record entry, and then clicking through multiple edit menus. It's copy-pasting IPs, verifying TTLs, and clicking 'Save'—a repetitive, time-consuming mess.
With the Cloud DNS MCP Server, you just tell your agent what needs changing. You say, 'Update the MX record for example.com to point to this new mail server.' Your agent runs `update_record` and the change is live. Period.
Cloud DNS (Anycast DNS Provider API) MCP Server: Control your records.
The tedious steps that vanish are the manual zone listing (`list_zones`), the record retrieval (`list_records`), and the sequential CRUD operations. No more jumping between tabs or systems just to confirm a value.
The difference is that you manage your entire global DNS layer through simple text commands. You don't touch a dashboard; you just talk to your agent.
Common Questions About Cloud DNS MCP
How do I list all zones using the Cloud DNS (Anycast DNS Provider API) MCP Server? +
You use the list_zones tool. It immediately retrieves a list of all DNS zones managed under your account. This is a quick way to see every domain you control.
What kind of records can I create with the Cloud DNS (Anycast DNS Provider API) MCP Server? +
The create_record tool handles A, AAAA, MX, CNAME, TXT, and more. It supports all common DNS record types you need to point services.
Can I update an existing record's TTL using the Cloud DNS (Anycast DNS Provider API) MCP Server? +
Yes, you use the update_record tool. You can specify the record and the new TTL value, modifying the record's behavior without deleting and recreating it.
Does the Cloud DNS (Anycast DNS Provider API) MCP Server let me delete a whole zone? +
Yes, the delete_zone tool allows you to remove an entire DNS zone. Be careful with this one; it removes the domain's entire record set.
How do I use the `create_record` tool to add a new DNS record? +
You pass the record type, name, and value parameters directly to the create_record tool. This handles the full CRUD operation for A, AAAA, MX, CNAME, and TXT records automatically.
What happens if I try to delete a record that doesn't exist using the `delete_record` tool? +
The server handles non-existent records gracefully, returning a clear error message indicating the record ID or zone was not found. Your AI agent can then proceed with other tasks.
Can I manage records in multiple zones with the Cloud DNS (Anycast DNS Provider API) MCP Server? +
Yes, you manage records across multiple zones by specifying the target zone ID or domain name in the prompt. Your AI client handles the context switching for you.
What is the best way to handle rate limits when updating records with the `update_record` tool? +
The MCP Server provides standard HTTP rate limit headers, which your AI client can read. If a limit is hit, your agent waits and retries the update_record call with an exponential backoff.
Can I list all DNS records for a specific zone ID? +
Yes! Use the list_records tool with the target Zone ID. The agent will return all configured records including A, MX, CNAME, and TXT entries.
How do I update the IP address of an existing A record? +
You can use the update_record tool. Provide the zone_id, record_id, and the new value (IP address). You can also optionally update the TTL at the same time.
Does this server support creating both Master and Slave zones? +
Yes. The create_zone tool allows you to specify the type as either 'master' or 'slave' when adding a new domain to your account.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
SparkPost
Bring your SparkPost email delivery platform into your AI. Manage templates, send campaigns, and audit deliverability directly from your editor.
Smarty
Equip your AI with enterprise-grade location intelligence to validate, autocomplete, and extract US or International addresses instantly.
RandomDuck
Brighten your day with random duck images, GIFs, and HTTP status ducks for developers.
You might also like
Percentage Calculation Engine
Stop LLMs from miscalculating discounts and interest. Deterministically calculate exact percentages and relative increases.
Ember Climate
Access global electricity data — generation, demand, emissions, and capacity from Ember Climate's open energy API.
MLflow (ML Lifecycle Management)
Manage ML lifecycle via MLflow — track training runs, monitor metrics, and audit the model registry.