nextdns-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEXTDNS_API_KEY | No | Your NextDNS API key | |
| NEXTDNS_READ_ONLY | No | Set to 'true' to enable read-only mode | |
| NEXTDNS_API_KEY_FILE | No | Path to a file containing the API key | |
| NEXTDNS_TEST_PROFILE | No | Profile ID for write operation tests | |
| NEXTDNS_DEFAULT_PROFILE | No | Optional default profile ID | |
| NEXTDNS_READABLE_PROFILES | No | Comma-separated list of readable profiles | |
| NEXTDNS_WRITABLE_PROFILES | No | Comma-separated list of writable profiles |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| manageProfilesA | Manage NextDNS profiles. NextDNS profiles are named configurations that contain DNS settings, blocklists,
analytics, and logs. Most other tools require a Operations:
- Examples:
- list: |
| manageSettingsA | Manage a settings category for a NextDNS profile. Settings categories:
- Operations:
- The Examples:
- get: |
| manageListsA | Manage allow/deny/block lists for a NextDNS profile. List types:
- Operations:
- Examples:
- get: |
| manageRewritesA | Manage DNS rewrite entries for a NextDNS profile. Rewrites let you return a custom answer for a hostname. Typical uses:
Operations:
- Examples:
- list: |
| manageLogsA | Manage query logs for a NextDNS profile. Operations:
- Time values can be Unix timestamps or relative strings like Examples:
- get recent: |
| queryAnalyticsA | Query NextDNS analytics metrics. Metrics:
- Set Optional filters:
- Examples:
- totals: |
| plotAnalyticsA | Generate a PNG line chart for a NextDNS analytics time-series metric. Use this to visualize query trends over time. The profile should have recent query history; otherwise the tool returns an error explaining that no data is available. Supported metrics: Time values can be Unix timestamps or relative strings like Examples:
- Returns: An MCP ImageContent PNG chart, or an error dict if data is unavailable. |
| dohLookupC | Perform a DNS-over-HTTPS lookup using a NextDNS profile. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| nextdns-usage-guide | Comprehensive guide for using the NextDNS MCP server tools |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools target distinct resources: profiles, settings, lists, rewrites, logs, analytics, plotting, and DoH lookup. However, manageSettings(category='logs') overlaps conceptually with manageLogs, and both manageProfiles update and manageSettings(general) can alter profile name, creating minor ambiguity.
All tools use camelCase consistently, with no mixing of snake_case or other conventions. The verb+noun pattern is mostly predictable, though dohLookup breaks the verb-first pattern slightly and manage* is reused across several resources.
8 tools is well-scoped for a NextDNS management server. Each tool covers a distinct area of the API and none appears redundant or superfluous.
The surface covers the core NextDNS lifecycle: profile CRUD, settings categories, allow/deny/block lists, rewrites, query logs, analytics querying, visualization, and DoH lookup. No obvious operational gap prevents common workflows, though device-level management could be an extension.