How to connect Nextdns to Hermes Agent
Connect Nextdns to Hermes with ClawLink: paste your Nextdns key once and 68 tools work from chat. No MCP server to run, nothing stored on your machine.
NextdnsAPI KEYMCPNextDNS is a DNS service that enhances internet security and privacy by blocking malicious websites, tracking scripts, and ads before they reach your device.. Once connected, Hermes Agent can read and act on Nextdns from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Nextdns access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Nextdns setup: pair once in the browser and your always-on Hermes agent can act on Nextdns for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Nextdns.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Nextdns
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Nextdns?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Nextdns in the ClawLink dashboard — paste your Nextdns API key once.
Verify the connection by asking Hermes:
Use Nextdns to download logs and walk me through the result in plain English.
Using a different agent?
The Hermes 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:
npx -y @useclawlink/cli loginlogin 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.
Nextdns MCP for Hermes
Looking for a Nextdns MCP server for Hermes Agent? ClawLink connects Nextdns to Hermes Agent and exposes 68 Nextdns tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Nextdns integration works the same way.
What the Hermes Agent Nextdns integration can do
68 Nextdns tools are ready for Hermes Agent 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 Hermes
| 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 |
Try it: find the Nextdns tool you need
Browse the 30 Nextdns tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Nextdns to download logs and walk me through the result in plain English.
Pull the relevant data from Nextdns, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Nextdns, summarize it in plain English, and point out anything that needs attention.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use Nextdns
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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.
FAQ
Is there a Hermes Agent Nextdns integration?
Yes. ClawLink is the fastest way to connect Hermes to Nextdns: link your Nextdns account once in the browser and Hermes Agent can call the Nextdns API through 68 ready-made tools — no custom code or token handling.
How do I connect Nextdns to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Nextdns in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Nextdns in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Nextdns working from chat.
Hermes paired but still can't use Nextdns
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Related
Hermes GitHub integration
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
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.