NS1 (IBM NS1 Premium DNS API) MCP. Automate global routing and DNS changes via chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
NS1 (IBM NS1 Premium DNS API) MCP Server connects your AI agent directly to global DNS infrastructure. You use this server to list, create, update, and delete entire DNS zones and individual records across multiple domains.
It lets you configure advanced traffic steering rules and set up monitoring jobs—all through natural conversation. Stop logging into web dashboards; manage all your network routing from your IDE.
What your AI agents can do
Create data source
Sets up a new external data feed source for NS1 to use in dynamic DNS responses.
Create monitoring job
Schedules a new job that tracks the health of specified endpoints across global regions.
Create record
Adds a brand-new DNS record (like A, CNAME, or TXT) to an existing zone.
Create, list, get details for, update, or delete entire domains (zones) within your NS1 account.
Add new records (create_record), retrieve specifics (get_record), modify existing records (update_record), and delete any DNS record type.
Set up monitoring jobs to check endpoint health, list available regions using list_monitoring_regions, or retrieve status reports using list_monitoring_jobs.
Manage external data feeds by listing sources (list_data_sources), creating new ones (create_data_source), and pushing real-time payloads via push_data_feed.
Modify the overall settings of a zone using update_zone, or read current configuration details with get_zone.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
NS1 (IBM NS1 Premium DNS API) MCP Server: 15 Tools
Manage your network infrastructure by calling tools for zone creation, record updates, monitoring job setup, and data feed management.
019e5d3dcreate data source
Sets up a new external data feed source for NS1 to use in dynamic DNS responses.
019e5d3dcreate monitoring job
Schedules a new job that tracks the health of specified endpoints across global regions.
019e5d3dcreate record
Adds a brand-new DNS record (like A, CNAME, or TXT) to an existing zone.
019e5d3dcreate zone
Provisions and sets up an entirely new domain zone within your NS1 account.
019e5d3ddelete record
Permanently removes a specific DNS record from its respective zone.
019e5d3ddelete zone
Decommissions and deletes an entire domain zone managed by NS1.
019e5d3dget record
Retrieves all specific details for a single, targeted DNS record type.
019e5d3dget zone
Fetches the current configuration and settings for an entire zone.
019e5d3dlist data sources
Lists all data sources currently connected or defined in your NS1 account.
019e5d3dlist monitoring jobs
Retrieves a list of all active and past monitoring jobs you've configured.
019e5d3dlist monitoring regions
Lists the geographical regions available for setting up new health checks.
019e5d3dlist zones
Returns a list of every DNS zone (domain) you currently manage in NS1.
019e5d3dpush data feed
Sends a payload of data to an existing, defined data feed source for dynamic responses.
019e5d3dupdate record
Modifies the value or parameters (like TTL) of an existing DNS record without deleting it first.
019e5d3dupdate zone
Changes the general settings, such as nameservers or policies, for a defined zone.
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 NS1 (IBM NS1 Premium DNS 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
Hey, listen up. The NS1 DNS API MCP Server plugs your AI agent straight into global DNS infrastructure. You use this server to manage everything—from setting up a brand-new domain zone right down to changing a single record's TTL. Forget logging into web dashboards; you handle all that complex network routing and configuration straight from your IDE.
Zone Lifecycle Management
You can list every DNS zone (domain) you manage in NS1 using list_zones. You’ll get the full setup details for any specific domain with get_zone, or you can modify general settings, like nameservers or policies, by running update_zone. If you need to provision an entirely new domain space, use create_zone to set it up.
When you're done with a zone, you decommission and delete the whole thing using delete_zone.
DNS Record CRUD Operations
You control every single record type—A, CNAME, TXT, whatever. To add a brand-new DNS record to an existing zone, just call create_record. If you need to modify an existing record's value or tweak its parameters without deleting it first, use update_record. You can pull up all the specific details for any targeted record type by running get_record, and if a record is trash, you wipe it out permanently with delete_record.
Network Health Monitoring
It's crucial to know if your endpoints are actually alive. You set up monitoring jobs using create_monitoring_job to track endpoint health across global regions. To see what job statuses you've got running or finished, check the list with list_monitoring_jobs. If you need to scope out where these checks can run, grab a list of available geographical regions by calling list_monitoring_regions.
Data Source Orchestration and Dynamic DNS
If your records depend on real-time data, this is how you handle it. You first check what external feeds are connected using list_data_sources. To bring a new data source online for dynamic responses, run create_data_source. Once that's set up, you push actual information to the feed via push_data_feed so your DNS responds with current data.
This keeps everything fresh and accurate.
Basically, this server gives you total control over setting up zones, managing records, checking endpoint health across multiple regions, and feeding dynamic responses from external sources—all without touching a web console.
How NS1 (IBM NS1 Premium DNS API) MCP Works
- 1 Subscribe to this server and provide your NS1 API Key.
- 2 Your AI client uses the key to authenticate against the NS1 APIs.
- 3 You prompt your agent with a natural language request (e.g., 'Update the CNAME record for staging.com'). The agent then runs the specific tool call (
update_record) and returns confirmation of the change.
The bottom line is you talk to your AI client, and it speaks directly to IBM NS1 to make infrastructure changes.
Who Is NS1 (IBM NS1 Premium DNS API) MCP For?
This is for the SRE or DevOps engineer who spends too much time clicking through multiple cloud dashboards just to change a single record. It's also for Cloud Architects needing to orchestrate complex, multi-region traffic steering rules without writing boilerplate API scripts.
Uses the agent to instantly check monitoring status (list_monitoring_jobs) or roll back records using delete_record during an incident.
Automates zone provisioning and record creation as part of a CI/CD workflow by calling tools like create_zone and create_record on demand.
Orchestrates complex traffic steering configurations or sets up global load balancing rules using conversational prompts that invoke the necessary APIs.
What Changes When You Connect
- Global Visibility: Instantly check the health of endpoints anywhere in the world. Use
list_monitoring_jobsto see what's running, then usecreate_monitoring_jobto add coverage for a new service endpoint. - Atomic Updates: You don't need multi-step scripts just to change one IP address. The
update_recordtool lets you modify an existing A or CNAME record directly via prompt, saving five minutes of SSH work every time. - Dynamic Routing Control: Don't rely on static IPs. By using tools like
create_data_sourceandpush_data_feed, your DNS responses can change based on real-time input (e.g., failover data). - Full Zone Lifecycle Management: Need to decommission an old service? You can run the full cleanup cycle—from
list_zonestodelete_recordand finallydelete_zone—all in conversation, ensuring nothing is left dangling. - Structured Deployment: Use
create_zonefirst. Then, define records usingcreate_record. This conversational process enforces a structured way of building out new domains without leaving your IDE.
Real-World Use Cases
Emergency Service Failover
The primary web service went down in the EU region. The SRE doesn't have time to log into the dashboard. They prompt their agent: 'Set all traffic for my-app.com to point to the backup IP address 203.0.113.5 and set a low TTL.' The agent runs update_record instantly, redirecting global traffic while the team investigates the root cause.
New Feature Rollout
A developer needs to test a new API endpoint in staging. Instead of manually creating the record, they ask their agent: 'Create an A record for api-staging.internal pointing to 10.0.0.5.' The agent runs create_record and confirms it's ready for testing.
Audit/Cleanup
A Cloud Architect suspects a zone is abandoned. They use list_zones, identify the old domain, run get_zone to review settings, and then call delete_zone. This ensures proper cleanup without manual dashboard interaction.
Dependency Tracking
The team needs to build a dynamic DNS response based on inventory data. They first use list_data_sources to check what's available, then call create_data_source, and finally push the initial records using push_data_feed.
The Tradeoffs
Forgetting TTL/Scope
The developer just tells their agent, 'Change this IP.' If they forget to specify a short Time-To-Live (TTL) or the target zone, the change might take hours or days to propagate globally.
→
Always check the record details first using get_record. When updating, explicitly mention the required TTL. Use update_record with all parameters defined to ensure immediate propagation.
Manual CLI scripting
Writing a long shell script that calls multiple API endpoints sequentially (curl ... | curl ...) and failing on the first network hiccup.
→
Use your agent. It manages the sequence of tool calls for you. For complex setups, prompt it to run create_record then update_zone, handling success/failure logic conversationally.
Using vague prompts
Prompting: 'Fix the DNS.' This gives no actionable steps and forces the agent to guess where the problem is.
→
Be precise. Start by querying status with list_monitoring_jobs or get_record. Then, tell it exactly what needs changing using tools like update_record.
When It Fits, When It Doesn't
Use this server if your core pain point is managing complex, multi-region DNS routing and record changes across multiple zones. You need the AI chat interface to act as a single pane of glass for infrastructure configuration. It's perfect for SRE teams that need rapid response capabilities.
Don't use it if you only need basic local network service discovery (like querying an internal, non-global DNS server). Also, don't try to run this as your sole CI/CD pipeline; while the tools support automation, dedicated infrastructure tooling is better for guaranteed transactional integrity. If your goal is just reading data, list_zones and get_record are sufficient, but if you need writes, this is what you want.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by NS1 (IBM NS1 Premium DNS API). 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 15 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
The old way: Dashboard clicking and SSH scripting.
Today, changing a single global record means logging into the web dashboard. You navigate to the zone, find the correct record, verify the TTL setting, click 'save,' and then wait for propagation time—all while juggling credentials or writing complex `dig` commands in an SSH session.
With this MCP server, you just talk. Tell your agent: 'Set my-app.com's A record to 192.0.2.1.' The agent runs the necessary tool calls (`update_record`) and confirms it. You get immediate, verifiable confirmation of the change, without touching a web GUI or SSH terminal.
NS1 (IBM NS1 Premium DNS API) MCP Server: Real-time infrastructure control.
Gone are the manual steps of checking zone status via `get_zone`, then logging into a separate monitoring tool to set up health checks, and finally running a script to update records. It's all one conversational flow.
The difference is control: you can orchestrate entire failover policies—from listing regions with `list_monitoring_regions` to creating the job (`create_monitoring_job`) that drives your DNS response using `push_data_feed`. You manage infrastructure through intent, not through clicks.
Common Questions About NS1 (IBM NS1 Premium DNS API) MCP
How do I list all my domains in NS1 using the MCP Server? +
Run the list_zones tool. It immediately returns a comprehensive list of every DNS zone you manage within your account, so you know exactly what you're working with before making any changes.
What is the difference between `create_record` and `update_record`? +
create_record builds a record that doesn't exist yet. Use it when you are launching something new. If the record already exists, use update_record to modify its value or parameters (like TTL) without deleting it.
Can I automate DNS changes as part of my workflow? +
Yes. The server supports this by allowing your AI agent to execute tools like create_zone and create_record based on a sequence of prompts, which is ideal for CI/CD integration.
How do I check the health status before making changes? +
You first call list_monitoring_jobs to see what's running. If you need new checks, use create_monitoring_job, specifying regions via list_monitoring_regions.
What do I need to check if my attempts to run `get_zone` return an access denied error? +
You must verify your NS1 API key. The server requires valid credentials linked to an active account to read zone data. Check the documentation for key generation and scope permissions.
How does the `push_data_feed` tool handle real-time, dynamic DNS updates? +
The tool accepts external data sources that drive immediate DNS responses. It pushes structured data directly to a specified feed endpoint, bypassing manual record creation for rapid changes.
Are there specific requirements I need to know before running `create_zone`? +
The API enforces standard domain naming conventions and checks for regional availability. We recommend listing existing zones first using list_zones to confirm uniqueness.
Before executing a potentially destructive command like `delete_record`, how can I verify its current settings? +
Always run get_record first. This confirms the exact details—including TTL, record type (A, CNAME), and associated zone—before you issue the delete command.
Can I create a new DNS zone using this server? +
Yes! Use the create_zone tool with the zone name (e.g., 'example.com'). You can also optionally set TTL, refresh, and expiry values during creation.
How do I add a record with specific answers for traffic steering? +
Use the create_record tool. You can provide a JSON array of answers (e.g., IP addresses) and a JSON array of filters to define how NS1 should steer traffic between those answers.
Can I see my active monitoring jobs and their status? +
Yes, the list_monitoring_jobs tool retrieves all configured monitoring jobs, allowing your AI agent to report on the health and status of your monitored endpoints.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Eden AI
Equip your AI agent to manage unified AI workflows, track providers, and monitor API usage via the Eden AI platform.
BlockPi (Distributed RPC Network)
Access distributed blockchain RPC nodes via BlockPi — monitor RU balances, track consumption, and execute JSON-RPC calls across multiple networks.
Beagle Security
Automate security testing via Beagle Security — list projects, start tests, and retrieve results directly from any AI agent.
You might also like
Zeev
Digitize business processes with BPMN workflows, electronic forms, and approval chains that replace paper and email chaos.
Giftpack
Send corporate gifts at scale with AI-curated selections that match recipient preferences and company budget guidelines.
Evoliz Invoicing & Management
Equip your AI agent to manage sales invoices, track CRM clients, and monitor quotes via the Evoliz API.