Skip to main content
Glama
dmeiser

nextdns-mcp

by dmeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to nextdns-mcp

No user-submitted related servers found.

    Related Servers

    • dns-mcp

      mclose
      F
      license
      Not graded
      quality
      B
      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
      -

    • cloudflare-mcp-server

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language management of Cloudflare services including Workers, KV, R2, D1, Queues, and more via the Model Context Protocol.
      1,333 npm
      Apache 2.0

    • FastlyMCP

      jackwrichards
      A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to interact with Fastly's CDN API through the Model Context Protocol, allowing secure management of CDN services, caching, security settings, and performance monitoring without exposing API keys.
      2
      13 npm
      7
      MIT

    • Cloudflare Control

      josephtandle
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Cloudflare infrastructure including DNS records, cache purging, SSL settings, Workers, and analytics through the Cloudflare API. Eliminates dashboard context-switching by allowing natural language control of domain management and infrastructure operations.
      -
    • Bitwarden MCP Server by bitwarden

      Bitwarden MCP Serverofficial

      bitwarden
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to securely manage Bitwarden vault items, folders, attachments, and organization administration through the Model Context Protocol.
      59
      1,718 npm
      258
      GPL 3.0
    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

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources