Skip to main content
Glama
Sign In
nextdns-mcp

nextdns-mcp

by dmeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to nextdns-mcp

No user-submitted related servers found.

    Related Servers

    • NextDNS-Agent-MCP

      Self-hosted-MCP
      A
      license
      A
      quality
      A
      maintenance
      Enables AI apps to inspect and manage a NextDNS account in plain language — profiles, analytics, query logs, blocklists, security and parental control settings — with every change saved and reversible via undo. It runs self-hosted on your own computer or server, keeps per-profile read/write/hidden permissions, and requires double confirmation for deletions or overwrites.
      23
      Apache 2.0
    • Koru Shield MCP Server

      Koru Shield MCP Serverofficial

      KoruShield
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to manage DNS filtering accounts by blocking or allowing domains, checking policies, reviewing blocked queries, and managing filter categories, schedules, and devices through natural language.
      16
      50 npm
      1
      MIT

    • dns-mcp

      mclose
      F
      license
      Not graded
      quality
      A
      maintenance
      Real-time DNS security analysis for AI assistants via MCP. Enables DNSSEC chain validation, email authentication posture, and registration intelligence directly from chat sessions.
      1
      -
    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