Cloud DNS MCP. Manage global records and zones via natural language.
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) lets you manage global domain records and zones using natural conversation. List, create, update, or delete any A, CNAME, MX, TXT record for your Anycast infrastructure directly through your AI client.
What your AI agents can do
Create record
Adds a completely new DNS record of any type to your target zone.
Create zone
Establishes an entirely new, empty DNS zone for you to manage.
Delete record
Removes a specific record from a zone; it's permanent.
Retrieve a list of all DNS zones associated with your account.
Set up an entirely new DNS zone for a specific domain name.
Fetch every record type (A, TXT, CNAME, etc.) within one target zone.
Change the value or parameters of an existing DNS record without deleting it first.
Add a brand new, specific type of DNS record to a zone.
Permanently remove an existing DNS record from the specified zone.
Remove an entire DNS zone and all its contained records.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Cloud DNS (Anycast DNS Provider API) with 7 Tools
These tools let you perform all standard CRUD operations on DNS, allowing your agent to manage zones and records from setup through deletion.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Cloud DNS (Anycast DNS Provider API) on Vinkius019e5d08create record
Adds a completely new DNS record of any type to your target zone.
019e5d08create zone
Establishes an entirely new, empty DNS zone for you to manage.
019e5d08delete record
Removes a specific record from a zone; it's permanent.
019e5d08delete zone
Deletes an entire DNS zone and all associated records.
019e5d08list records
Pulls a list of every existing record inside a specific, named zone.
019e5d08list zones
Gives you an overview and names of all the zones under your account.
019e5d08update record
Changes the values or settings on a record that is already in place.
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,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ 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
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.
Changing DNS records always feels like navigating a labyrinth of clicks.
Today, changing a simple pointer—say, redirecting an old subdomain to a new microservice—means logging into the provider's portal. You find the zone, click 'Records,' locate the specific CNAME record, manually edit the value, and hit save. If you have five different domains or multiple records in one domain, that's five times the clicking and copying.
With this MCP, you just tell your agent: 'Change the subdomain pointer to the new IP.' The agent handles finding the right zone, locating the correct record, and applying the change—all from a single prompt. You get the result without ever opening a dashboard.
Using `create_record` and `update_record` makes network changes feel like typing.
The tedious parts that disappear are locating the right record type (A, CNAME, etc.), verifying the zone ID, and manually ensuring you didn't delete the wrong entry. The agent does this internal mapping for you.
You stop thinking about API calls and start focusing on the network architecture itself. You simply state the change, and it happens.
What you can do with this MCP connector
You can use this MCP to handle complex network configurations without clicking through a dashboard. Need to point a subdomain to a new service? Or maybe you need to verify ownership by adding a specific TXT record? Your agent handles it all.
Instead of logging into a console and executing multiple commands, you tell your AI client what needs fixing—for instance, 'Update the MX records for example.com'—and it manages the change across zones and records. If you are building complex automation that spans different services, remember that Vinkius handles all credentials through a zero-trust proxy.
Your API keys stay in transit but never sit on disk; this keeps your entire infrastructure secure while giving your agent full control over DNS.
This connector gives deep access to zone management and record controls, letting you audit or modify anything from A records to SRV entries using simple text commands.
019e5d08-bcc3-7279-a5d5-371ff6ae1942 
How Cloud DNS MCP Works
- 1 Subscribe to this MCP in Vinkius and provide your Cloud DNS API key.
- 2 Connect the MCP to your preferred AI client (Cursor, Claude, etc.).
- 3 Tell your agent what you need done; it executes the necessary zone or record changes through the API.
The bottom line is you get precise control over your global DNS settings using natural language instructions instead of a GUI.
Who Is Cloud DNS MCP For?
This connector is for engineers and admins who spend too much time manually checking dashboards or running scripts just to update domain pointers. If your job involves keeping services reachable via the internet, this is for you.
Automating DNS record provisioning during CI/CD pipelines and ensuring service endpoints are always correct.
Managing global Anycast zones across multiple environments or regions using simple chat commands instead of complex CLI scripts.
Quickly testing domain validation or updating TXT records for OAuth/verification straight from their IDE prompt.
What Changes When You Connect
- Automate full lifecycle management: You can
create_zone, then uselist_recordsto verify the initial state, all without manual dashboard switching. This speeds up deployment cycles significantly. - Handle complex changes safely: If a record needs adjusting, you don't delete it; you use
update_record. This preserves history and reduces human error compared to full recreation. - Audit instantly: Need to know what records exist right now? Running
list_recordsgives you an instant snapshot of everything in scope for troubleshooting. - Build reliable workflows: Use the MCP to chain actions, like first calling
create_zonethen immediately usingcreate_recordto point a service. It's repeatable and traceable. - Full control over deletion: You can safely remove assets by running
delete_recordsordelete_zones, making cleanup part of your automation routine.
Real-World Use Cases
A new microservice needs a public endpoint.
The developer asks the agent to point 'api.new-app.com' to the latest server IP address. The agent uses create_record (for an A record) and specifies the correct zone, completing the deployment in one step.
A domain migration requires changing multiple records.
The sysadmin tells the agent to update all CNAME and MX records for a specific zone. The agent uses update_record across dozens of entries, preventing manual copy/pasting errors.
Debugging DNS resolution failures.
A user suspects outdated settings. They prompt the agent to run list_records for the affected zone, instantly getting a dump of all current configurations to check against the expected setup.
Decommissioning an old project site.
Instead of logging in and deleting records one by one, the agent is told to delete_zone for the entire subdomain. Everything linked to that zone vanishes instantly.
The Tradeoffs
Trying to manage everything manually.
Opening 15 browser tabs, copying IPs into fields, and clicking 'Save' for every single record change. This is slow and error-prone.
→
Let your agent handle it. Use create_record or update_record via a simple command prompt. The MCP handles the API calls so you don't have to touch a dashboard.
Ignoring zone structure when making changes.
Attempting to modify a record that belongs to an incorrect or non-existent zone, resulting in ambiguous API errors and lost time.
→
Always check the zone first. Use list_zones to verify your domain is properly set up before attempting any specific operations like create_record.
Over-relying on listing tools.
Running list_records repeatedly during an active deployment, which creates unnecessary read load and slows down the agent's response time.
→
Only use list_records for initial auditing or debugging. If you know exactly what needs changing, skip listing and go straight to update_record.
When It Fits, When It Doesn't
Use this MCP if your job requires programmatic management of domain names, IPs, and service endpoints. You need to automate the creation, modification, or deletion of DNS records across multiple zones. Don't use it if you just need to check a single record value; in that case, basic lookup services might suffice. This tool is overkill for simple tasks but perfect for complex workflows: combining list_zones with update_record, for example, allows an agent to automatically discover all domains and then systematically update their SSL certificates. If you only need read access, consider a dedicated read-only API wrapper instead.
Common Questions About Cloud DNS MCP
How do I list all my domains using the `list_zones` tool? +
You use the list_zones function to get a comprehensive list of every zone associated with your account. This is the first step before you can target any specific records for management.
Can I create multiple record types at once with `create_record`? +
You must generally use separate calls to create_record for different record types (like one call for an A record and another for a TXT record). The agent handles the sequence if you list them out.
What's the difference between `update_record` and `create_record`? +
Update_record is for making changes to something that already exists. Use it when the record type and zone are correct, but the value needs changing. Use create_record if you are adding a brand new entry.
If I use `delete_zone`, does it delete all records too? +
Yes. Using delete_zone removes the entire DNS zone and everything within it, making this operation irreversible for the targeted domain name.
How do I audit all records for a domain using the `list_records` tool? +
It retrieves every record associated with your specified zone. This is key for auditing configurations or troubleshooting resolution problems without manually checking the dashboard.
What credentials are needed to use the `create_zone` tool? +
You must provide a Cloud DNS Auth Key (API Key). This key authorizes your agent and ensures secure access when connecting through any MCP-compatible client.
When should I use `update_record` instead of calling `create_record`? +
Use it specifically to change an existing record's value, TTL, or priority. It modifies the data in place without first deleting the original entry.
What happens if I try to `create_record` for a name that already exists? +
The tool will report a conflict error, preventing accidental overwrites. You'll need to either use update_record or adjust the record's unique identifier before running the command again.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.