Skip to main content
Glama
SveinT83

Domeneshop MCP

by SveinT83
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Domeneshop MCP

No user-submitted related servers found.

    Related Servers

    • REG.RU MCP Server

      AlekMel
      A
      license
      B
      quality
      B
      maintenance
      Enables managing REG.RU domain names, DNS zones and records, services, billing, DNSSEC, and account folders through REG.API 2.0 over the Model Context Protocol. Provides tools, resources, and prompts for domain availability checks, DNS record edits, renewals, balance and invoice lookups, plus workflows like expiring-service audits and VPS domain configuration.
      18
      MIT

    • cloudflare-mcp

      tecnomanu
      F
      license
      Not graded
      quality
      B
      maintenance
      Manages DNS records and Cloudflare Tunnels for a Cloudflare zone via the Cloudflare API. Supports listing, creating, updating, and deleting DNS records, as well as tunnel lifecycle operations.
      8 npm
      -

    • spaceship-mcp

      heaventree
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for reading and changing DNS records via the Spaceship API, with reviewable two-step confirmation and safety restrictions. It exposes only safe DNS operations, using domain allowlisting and failing closed when not configured.
      143 npm
      MIT

    • mcp-cloudflare

      itunified-io
      A
      license
      B
      quality
      C
      maintenance
      Slim Cloudflare MCP Server — 42 tools for managing DNS, zones, tunnels, WAF, Zero Trust, and security via Cloudflare API v4. Multi-zone support. No SSH, no shell, API-only with 3 runtime dependencies. AGPL-3.0 + Commercial dual-licensed.
      96
      65 npm
      AGPL 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

    B3.3/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools have clearly distinct targets (domains vs DNS records vs forwards vs invoices vs plans), and the preview/apply convention is applied consistently. However, several high-level DNS writers (ensure_dns_records, setup_website, replace_ip, copy_dns_records, add_verification_txt) overlap with the primitive create/update/delete_dns_record tools, so an agent must read carefully to choose the right one.

    Naming Consistency4/5

    Nearly all names follow a predictable snake_case verb_noun pattern (list_domains, create_dns_record, update_forward, apply_plan). The only real deviation is the noun-first account_overview, which is a minor cosmetic inconsistency.

    Tool Count3/5

    27 tools is heavy for a single server and sits above the comfortable 3-15 range. The scope is genuinely broad (domains, DNS, forwards, DDNS, invoices, backups, plan lifecycle), so most tools earn their place, but the count is borderline for what could be split.

    Completeness4/5

    Coverage is strong: full DNS record CRUD, forwards CRUD, DDNS, invoice retrieval, batch planning, zone export, audit, and backup/restore. The main gap is domain registration lifecycle (no create/delete/transfer/nameserver-set operations on the domain itself), but core DNS and account workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources