
Cloud DNS Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_5XmEhg2JVh0rFgVfyO3zB7a7ZChuVONWYlYtNbim/mcpConnecting Cloud DNS to Grok
About a minute, at grok.com/connectors
- 1In Grok, open grok.com/connectors and click New Connector.
- 2Choose Custom, name it, and paste your Cloud DNS link as the remote MCP server URL.
- 3Save and enable it, finish the browser authorization if prompted, and ask Grok something real. Cloud DNS is now part of your Grok.
{
"mcpServers": {
"cloud-dns-anycast-dns-provider-api-mcp": {
"url": "https://edge.vinkius.com/vk_preview_5XmEhg2JVh0rFgVfyO3zB7a7ZChuVONWYlYtNbim/mcp"
}
}
}Grok + Cloud DNS
One chat. Your Cloud DNS, live inside Grok.
Real prompts, answered with live data. This is the kind of conversation you will have in Grok once the connector is in.
Waiting for input…
Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.
These prompts ship with the Cloud DNS Connector. Once yours is connected, they work in your sessions.
The full capability set, the prompts and the observed latency live on the Cloud DNS Connector page.
Mission Control
See everything your Grok agents do in Cloud DNS.
When Grok runs a tool in Cloud DNS, it happens on Grok's side: you see the answer in the chat, but not the request itself, what data it carried, or whether a rule was broken.
Now every move lands on your screen.
Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.
Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.
AI Agents Activities
last 30 daysRequest Volume & Latency
requests latencyEvery request your Grok agents make through Cloud DNS is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your Cloud DNS workflows.
What sets us apart
It's not just the Connector that stays safe. Everything your agents do through it is.
Connecting Cloud DNS to your AI is step one. But an open line between your agents and Cloud DNS is only half the story: without protection, every action they take runs unguarded.
That's why protection doesn't stop at the door.
Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.
Tamper Proof Activity Log
Every request your agents make in Cloud DNS is recorded and signed, so any change to the history becomes detectable.
Automatic Key Rotation
We rotate security keys every 24 hours. Your Cloud DNS connection stays protected without any manual work.
Spending Protection
We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your Cloud DNS actions never surprise you.
Isolated Sandbox
Every execution through Cloud DNS runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.
Security Event Streaming
Security events flow to Splunk, Datadog or your own webhook, so Cloud DNS activity lands in the tools you already rely on.
Instant Resume
Idle connections resume in 3 to 5 ms while preserving their state, keeping your Grok sessions responsive.
Malicious File Protection
We detect compressed files designed to exhaust system resources and block them before they ever reach Cloud DNS.
Credential Validation
We test your Cloud DNS credentials before saving them. Invalid credentials are rejected instead of being stored.
Separate Usage Limits
Usage stays isolated per account, so activity in one connection never consumes another account's allowance.
One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.
These guarantees are not add-ons: they are the infrastructure every Cloud DNS connection runs on. Read how our infrastructure protects everything your Grok agents do, end to end.
Inside Vinkius
Get Cloud DNS ready for your AI. It's easy.
You choose Cloud DNS from the Vinkius Catalog, sign in to your Cloud DNS account, and get one connection link. That's it.
You choose Cloud DNS
You find Cloud DNS in the Catalog and install the Connector with one click.
Cloud DNS
Active
Enable ConnectorActivating…You sign in
You connect your Cloud DNS account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.
Configure Credentials
Configure credentials for {{connectorName}}
RequiredEncryptedSave & ContinueYou add the link in Grok
Vinkius gives you one connection link. At grok.com/connectors, you click New Connector, choose Custom, and paste the link as the remote MCP server URL.
Token generated successfully
MCP Connection URL
https://edge.vinkius.com/vk_preview_5XmEhg2JVh0rFgVfyO3zB7a7ZChuVONWYlYtNbim/mcpGo to DashboardConnection Token
vk_live_••••••••
Set it up once. Use Cloud DNS with the AI you already use.
FAQ
Grok access questions.
- 01
Does this work in the Grok mobile apps?
Yes. On mobile you go to Settings and then Connectors; on the web the management page is grok.com/connectors. The same connector link works in both.
- 02
If I connect Cloud DNS to Grok, can I use the same connection in Claude or ChatGPT later?
Yes, and that's the point: the connection is yours, not Grok's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and Cloud DNS is already there.
- 03
Do I need to hand my Cloud DNS password to Grok?
Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Grok only ever sees the link, and you can remove it whenever you want.
- 04
What can I actually ask Grok to do with Cloud DNS?
Whatever the Connector covers: check data, run actions and bring answers back into the chat. The Connector page lists every capability your AI gains, with real examples you can copy.
- 05
Grok doesn't show the Connector. What do I check?
Reopen grok.com/connectors and make sure your connector is enabled, confirm the link was pasted exactly as copied, and confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.
- 06
Can I remove the access later?
Anytime. Remove the connector at grok.com/connectors and it's out of your chats. Your Vinkius account keeps the connection and its history either way, ready for the next AI.
More questions about Cloud DNS? The Connector page answers them. See everything the Cloud DNS Connector can do
About the Connector
What Cloud DNS adds to your AI.
Once you connect it, your AI gains 7 capabilities: the exact actions it can take in Cloud DNS when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.
See everything the Cloud DNS Connector can do