Google Cloud DNS MCP Server
Enables AI assistants to manage Google Cloud DNS zones and records, supporting full CRUD operations for various record types and DNSSEC management. It provides secure service account authentication to interact directly with Google Cloud's global DNS infrastructure.
README
Google Cloud DNS MCP Server
A comprehensive Model Context Protocol (MCP) server for managing Google Cloud DNS managed zones and records via the Google Cloud DNS API. This server enables AI assistants like Claude to manage DNS infrastructure directly through Google Cloud's robust DNS service.
Features
🌐 Managed Zone Operations
- List Zones: View all DNS managed zones in your project
- Zone Details: Get comprehensive zone information including name servers and DNSSEC status
- Zone Visibility: Support for both public and private zones
📝 DNS Record Management
- Full CRUD: Complete create, read, update, delete operations for DNS records
- Record Types: Support for A, AAAA, CNAME, MX, NS, SOA, PTR, SRV, TXT, CAA
- Smart Filtering: Filter records by type or name
- TTL Management: Full control over time-to-live settings
- Batch Changes: Atomic operations with change tracking
🛡️ Enterprise Security
- Service Account Auth: Secure service account-based authentication
- IAM Integration: Leverages Google Cloud IAM for fine-grained permissions
- Audit Trail: All changes tracked through Google Cloud's audit logging
- DNSSEC Support: Full support for DNSSEC-enabled zones
⚡ Performance & Reliability
- Global Infrastructure: Built on Google Cloud's global DNS network
- Change Tracking: Monitor and wait for DNS propagation
- Error Handling: Comprehensive error handling with clear messages
- Type Safety: Full TypeScript support
Quick Start
Run the server directly with npx (requires Node.js 18+):
npx @artik0din/mcp-gcloud-dns
Or install locally:
npm install -g @artik0din/mcp-gcloud-dns
mcp-gcloud-dns
Environment Variables
Create a .env file in your working directory:
| Variable | Required | Description |
|---|---|---|
GOOGLE_CLOUD_PROJECT_ID |
✅ | Your Google Cloud project ID |
GOOGLE_CLOUD_CREDENTIALS |
✅ | Service account JSON credentials as a string |
Setting Up Google Cloud Credentials
1. Create a Service Account
- Go to Google Cloud Console > IAM & Admin > Service Accounts
- Click "Create Service Account"
- Enter a name (e.g.,
dns-mcp-server) - Click "Create and Continue"
2. Grant DNS Permissions
Grant one of these roles to your service account:
- DNS Administrator (full access) -
roles/dns.admin - Custom Role with these permissions:
dns.managedZones.listdns.managedZones.getdns.resourceRecordSets.listdns.changes.createdns.changes.get
3. Create and Download Key
- Click on your service account
- Go to "Keys" tab
- Click "Add Key" > "Create new key"
- Choose JSON format
- Download the key file
4. Set Environment Variables
# Your project ID
export GOOGLE_CLOUD_PROJECT_ID="your-project-id"
# Service account JSON as a string (escape quotes)
export GOOGLE_CLOUD_CREDENTIALS='{"type":"service_account","project_id":"your-project",...}'
MCP Client Configuration
Claude Desktop
Add this to your Claude Desktop configuration:
{
"mcpServers": {
"google-cloud-dns": {
"command": "npx",
"args": ["@artik0din/mcp-gcloud-dns"],
"env": {
"GOOGLE_CLOUD_PROJECT_ID": "your-project-id",
"GOOGLE_CLOUD_CREDENTIALS": "{\"type\":\"service_account\",\"project_id\":\"your-project\",...}"
}
}
}
}
Other MCP Clients
Use the command npx @artik0din/mcp-gcloud-dns with the appropriate environment variables set.
Available Tools
gcloud_dns_list_zones
List all DNS managed zones in your Google Cloud project.
Parameters: None
Example:
List all my Google Cloud DNS zones
Show all managed zones in the project
gcloud_dns_get_zone
Get detailed information about a specific managed zone.
Parameters:
zoneName(string, required): Managed zone name (not the DNS name)
Example:
Get details for zone my-example-zone
Show information about production-dns-zone
gcloud_dns_list_records
List DNS records in a managed zone with optional filtering.
Parameters:
zoneName(string, required): Managed zone nametype(string, optional): Filter by record type (A, AAAA, CNAME, MX, TXT, etc.)name(string, optional): Filter by record name (must include trailing dot)
Example:
List all records in zone my-example-zone
Show A records in zone production-dns
Get records for www.example.com. in zone my-zone
gcloud_dns_create_record
Create a new DNS record in a managed zone.
Parameters:
zoneName(string, required): Managed zone namename(string, required): Record name (must end with zone's DNS name and trailing dot)type(string, required): Record type (A, AAAA, CNAME, MX, TXT, etc.)ttl(number, optional): TTL in seconds (defaults to 300)rrdatas(array, required): Array of record data values
Example:
Create A record for www.example.com. pointing to 1.2.3.4 in zone my-zone
Add CNAME record for blog.example.com. pointing to www.example.com. with TTL 3600
Create MX record for example.com. with priority 10 pointing to mail.example.com.
gcloud_dns_update_record
Update an existing DNS record.
Parameters:
zoneName(string, required): Managed zone namename(string, required): Record name to updatetype(string, required): Record typettl(number, optional): New TTL in secondsrrdatas(array, required): New record data values
Example:
Update A record for www.example.com. to point to 5.6.7.8 in zone my-zone
Change TTL of CNAME record blog.example.com. to 7200 seconds
Update MX record for example.com. to use new mail server
gcloud_dns_delete_record
Delete a DNS record from a managed zone.
Parameters:
zoneName(string, required): Managed zone namename(string, required): Record name to deletetype(string, required): Record type
Example:
Delete A record for old.example.com. from zone my-zone
Remove CNAME record for staging.example.com.
Delete TXT record for verification.example.com.
DNS Record Types
The server supports all standard DNS record types available in Google Cloud DNS:
- A: IPv4 address records
- AAAA: IPv6 address records
- CNAME: Canonical name records (aliases)
- MX: Mail exchange records
- NS: Name server records
- SOA: Start of authority records (managed by Google Cloud)
- PTR: Pointer records (reverse DNS)
- SRV: Service records
- TXT: Text records (SPF, DKIM, verification, etc.)
- CAA: Certification Authority Authorization records
Important Notes
DNS Name Format
- All DNS names must end with a trailing dot (e.g.,
www.example.com.) - Names must be within the zone's DNS namespace
- Use
@or the zone's DNS name for apex records
Change Propagation
- DNS changes are processed asynchronously by Google Cloud
- The server waits for changes to complete before returning
- Changes typically propagate within seconds to minutes globally
Record Restrictions
- Cannot delete NS or SOA records (required for DNS functionality)
- CNAME records cannot coexist with other record types for the same name
- MX and SRV records require priority values
Security Considerations
- Service Account Security: Store service account keys securely
- Least Privilege: Grant minimal required DNS permissions
- Key Rotation: Rotate service account keys regularly
- Environment Variables: Never commit credentials to version control
- Project Isolation: Use separate projects for different environments
Error Handling
The server provides detailed error messages for common scenarios:
- Authentication errors: Check service account credentials and permissions
- Zone not found: Verify zone name and project access
- Record conflicts: CNAME conflicts, duplicate records
- Invalid data: Malformed DNS names, invalid IP addresses
- Permission denied: Insufficient IAM permissions
- Quota exceeded: Google Cloud API quotas
Development
# Clone the repository
git clone https://github.com/artik0din/mcp-gcloud-dns.git
cd mcp-gcloud-dns
# Install dependencies
npm install
# Build the project
npm run build
# Run locally
npm start
Troubleshooting
Common Issues
-
"Authentication failed"
- Verify GOOGLE_CLOUD_CREDENTIALS is valid JSON
- Check service account has DNS permissions
- Ensure project ID is correct
-
"Zone not found"
- Check zone name (use zone name, not DNS name)
- Verify zone exists in the specified project
- Ensure service account has access to the zone
-
"Record already exists"
- Use update operation instead of create
- Check for CNAME conflicts
- Verify exact record name and type
API Compatibility
This server uses Google Cloud DNS REST API v1. It supports:
- All managed zone operations
- All DNS record types supported by Cloud DNS
- Change tracking and status monitoring
- Both public and private zones
License
MIT License - see LICENSE file for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Credits
Built with:
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.