# How to connect Nextdns to OpenClaw (paste one key, 68 tools) > Connect Nextdns to OpenClaw with ClawLink: paste your Nextdns key once and 68 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/nextdns The usual route to Nextdns access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Nextdns setup: install one ClawHub skill, connect Nextdns in the browser, and OpenClaw can call real Nextdns actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Nextdns. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Nextdns** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect nextdns # connect Nextdns (browser OAuth) npx -y @useclawlink/cli actions nextdns # list available actions npx -y @useclawlink/cli run nextdns --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Nextdns in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Nextdns API key once. Verify the connection by asking OpenClaw: > Use Nextdns to download logs and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Nextdns is connected in the dashboard, that agent calls the same 68 Nextdns tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Nextdns MCP for OpenClaw Looking for a Nextdns MCP server for OpenClaw? ClawLink connects Nextdns to OpenClaw and exposes 68 Nextdns tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Nextdns integration](https://claw-link.dev/hermes/nextdns) works the same way. ## What the OpenClaw Nextdns integration can do 68 Nextdns tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 68. ### 30 of 68 Nextdns tools for OpenClaw | Tool | What it does | |---|---| | **Download logs** `nextdns_download_logs` | Retrieves the download URL for exported DNS query logs from a NextDNS profile | | **Get allowlist** `nextdns_get_allowlist` | Retrieve the list of allowed domains for a NextDNS profile | | **Get analytics destinations** `nextdns_get_analytics_destinations` | Retrieve destination analytics for a profile showing query destinations by country or GAFAM | | **Get analytics devices2** `nextdns_get_analytics_devices2` | Retrieve device analytics for a profile showing identified devices with names, models, and | | **Get analytics dnssec** `nextdns_get_analytics_dnssec` | Retrieve DNSSEC validation analytics for a profile showing validated vs non-validated query | | **Get analytics domains** `nextdns_get_analytics_domains` | Retrieve analytics data for domains within a specific profile | | **Get analytics encryption** `nextdns_get_analytics_encryption` | Retrieve encryption analytics for a profile showing encrypted vs unencrypted query counts | | **Get analytics ip versions** `nextdns_get_analytics_ip_versions` | Retrieve analytics grouped by IP version within a specific profile | | **Get analytics ips** `nextdns_get_analytics_ips` | Retrieve analytics aggregated by client IP addresses | | **Get analytics protocols** `nextdns_get_analytics_protocols` | Retrieve protocol analytics for a specific profile showing DNS protocol distribution | | **Get analytics query types** `nextdns_get_analytics_query_types` | Retrieve DNS query counts broken down by query type | | **Get analytics reasons2** `nextdns_get_analytics_reasons2` | Retrieve blocking reasons analytics showing blocklists, native tracking protection, and other | | **Get analytics status** `nextdns_get_analytics_status` | Retrieve analytics status for a specific profile | | **Get logs** `nextdns_get_logs` | Retrieve logs for a specific NextDNS profile with optional filters | | **Get parental control** `nextdns_get_parental_control` | Get parental control settings for a profile | | **Get parental control categories** `nextdns_get_parental_control_categories` | Get the list of blocked/allowed content categories for parental control | | **Get parental control services** `nextdns_get_parental_control_services` | Get the list of blocked/allowed services for parental control | | **Get performance settings** `nextdns_get_performance_settings` | Get performance settings for a profile including ECS, cache boost, and CNAME flattening | | **Get privacy settings** `nextdns_get_privacy_settings` | Get privacy settings for a profile including blocklists, native tracking settings, disguised | | **Get profile** `nextdns_get_profile` | Retrieves the details of a specific NextDNS profile | | **Get rewrites** `nextdns_get_rewrites` | Retrieve the list of DNS rewrites for a NextDNS profile | | **Get security tlds** `nextdns_get_security_tlds` | Get the list of blocked TLDs (top-level domains) for a profile's security settings | | **Get settings** `nextdns_get_settings` | Get all settings for a NextDNS profile including logs, block page, performance, and web3 | | **Get settings blockpage** `nextdns_get_settings_blockpage` | Retrieve the block page settings for a NextDNS profile | | **Get settings logs** `nextdns_get_settings_logs` | Retrieve the logging settings for a NextDNS profile | | **List denylist domains** `nextdns_list_denylist_domains` | List domains in the denylist for a profile | | **List profiles** `nextdns_list_profiles` | List all NextDNS profiles for the authenticated user, returning profile IDs and configurations | | **List security settings** `nextdns_list_security_settings` | List current security options for a NextDNS configuration | | **Add allowlist entry** `nextdns_add_allowlist_entry` | Add a domain to the allowlist of a NextDNS profile | | **Add blocked tld** `nextdns_add_blocked_tld` | Add a top-level domain to the security blocklist for a NextDNS profile | ## Example prompts **Download Logs** > Use Nextdns to download logs and walk me through the result in plain English. **Get Allowlist** > Pull the relevant data from Nextdns, summarize it in plain English, and point out anything that needs attention. **Get Analytics Destinations** > Pull the relevant data from Nextdns, summarize it in plain English, and point out anything that needs attention. **Get Analytics Devices2** > Pull the relevant data from Nextdns, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Nextdns working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Nextdns API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Nextdns account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Nextdns. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Nextdns actions to the runtime in a format your agent can reliably use. | 68 tools for Nextdns are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Nextdns to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Nextdns in the browser, and the 68 tools above work from chat. There is no SDK and no config file, and the Nextdns key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Nextdns skill but can't call the tools The ClawHub skill teaches OpenClaw about Nextdns, but the calls run through the ClawLink plugin and your connected account. Make sure Nextdns is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Nextdns from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Nextdns tools Nextdns tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Nextdns call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Nextdns returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Nextdns has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Nextdns integration? Yes. ClawLink is the fastest way to connect OpenClaw to Nextdns: link your Nextdns account once in the browser and OpenClaw can call the Nextdns API through 68 ready-made tools — no custom code or token handling. ### How do I add Nextdns to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Nextdns skill from ClawHub, then you click Connect in the dashboard to authorize Nextdns. OpenClaw calls the tools from the next message — no config files, and the Nextdns key you paste is stored server-side instead of in your environment. ### How long does it take to connect Nextdns to OpenClaw? About two minutes. Sign in, click Connect next to Nextdns in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Nextdns up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Nextdns working from chat. ### OpenClaw installed the Nextdns skill but can't call the tools The ClawHub skill teaches OpenClaw about Nextdns, but the calls run through the ClawLink plugin and your connected account. Make sure Nextdns is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.