Skip to main content
Glama
Sign In
nextdns-mcp

nextdns-mcp

by dmeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NEXTDNS_API_KEYNoYour NextDNS API key
NEXTDNS_READ_ONLYNoSet to 'true' to enable read-only mode
NEXTDNS_API_KEY_FILENoPath to a file containing the API key
NEXTDNS_TEST_PROFILENoProfile ID for write operation tests
NEXTDNS_DEFAULT_PROFILENoOptional default profile ID
NEXTDNS_READABLE_PROFILESNoComma-separated list of readable profiles
NEXTDNS_WRITABLE_PROFILESNoComma-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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
manageProfilesC

Manage NextDNS profiles.

NextDNS profiles are named configurations that contain DNS settings, blocklists, analytics, and logs. Most other tools require a profile_id from this tool.

manageSettingsC

Manage a settings category for a NextDNS profile.

manageListsC

Manage allow/deny/block lists for a NextDNS profile.

manageRewritesC

Manage DNS rewrite entries for a NextDNS profile.

Rewrites let you return a custom answer for a hostname. Typical uses:

  • Point an internal hostname to a private IP.

  • Block a domain by rewriting it to 0.0.0.0.

manageLogsC

Manage query logs for a NextDNS profile.

queryAnalyticsD

Query NextDNS analytics metrics.

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: status, devices, protocols, queryTypes, ipVersions, dnssec, encryption, reasons, ips.

Time values can be Unix timestamps or relative strings like -1d.

The ;series endpoint takes no limit parameter: limit is part of this tool's published surface, is rejected above 500 rather than clamped, and is never forwarded, so the requested range is the only thing that bounds the response. Three server-side limits are enforced before the request is built, and each is rejected with an invalid_argument error naming the limit rather than silently adjusted:

  • interval must be between 60 and 86400 seconds.

  • limit must not exceed 500.

  • The range must be interpretable (a Unix timestamp, an ISO 8601 timestamp, now, or a relative offset such as -7d; a relative unit letter is read case-sensitively and a timestamp with no timezone is read as UTC), must end after it starts, and spans at most 2000 intervals (at most 2000 points per series), so a wide range needs a proportionally larger interval.

dohLookupC

Perform a DNS-over-HTTPS lookup using a NextDNS profile.

Prompts

Interactive templates invoked by user choice

NameDescription
nextdns-usage-guideComprehensive guide for using the NextDNS MCP server tools

Resources

Contextual data attached and managed by the client

NameDescription
nextdns-usage-guideComprehensive guide for using the NextDNS MCP server tools
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.8/5.0

Scored across 8 tools

Disambiguation4/5

Each of the five manage* tools targets a clearly distinct NextDNS resource (profiles, lists, settings, rewrites, logs), so misselection is unlikely. The only pair with potential overlap is queryAnalytics vs plotAnalytics, but the descriptions clearly separate raw metrics from chart rendering, and dohLookup is unique.

Naming Consistency4/5

Five tools follow a uniform snake_case-ish camelCase 'manage<Resource>' pattern, and queryAnalytics/plotAnalytics are consistent verb+noun camelCase. The only deviation is dohLookup, which puts the noun (DoH) before the verb, and the generic 'manage' verb hides which sub-operations are supported.

Tool Count5/5

Eight tools is well within the sweet spot and each maps to a real NextDNS capability area. Nothing appears redundant or missing at the count level; the analytics surface is split into query and plot, which is justified by distinct outputs (JSON metrics vs PNG).

Completeness4/5

The surface covers profiles, lists, settings, rewrites, logs, DoH resolution, and analytics query/visualization, which is essentially the whole NextDNS feature set. Minor gaps exist around account/API-key-level operations and configuration export/import, but core lifecycle coverage per resource is present.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources