Skip to main content
Glama
habib-alqalam

cloudflare-mcp

by habib-alqalam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to cloudflare-mcp

No user-submitted related servers found.

    Related Servers

    • cloudflare-mcp

      tecnomanu
      A
      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.
      3 npm
      MIT

    • Cloudflare MCP Server

      jeffgolden
      A
      license
      B
      quality
      D
      maintenance
      Exposes Cloudflare DNS, security, redirects and zone-settings functionality as structured tools that AI assistants like Claude Desktop can invoke directly.
      18
      16 npm
      MIT

    • cloudflare-mcp

      Steph-ux
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a unified MCP interface to manage Cloudflare services including DNS, compute (Workers, KV, D1), storage (R2), AI, security, Radar, and a universal API gateway for any Cloudflare v4 endpoint.
      MIT

    • Domeneshop MCP

      SveinT83
      A
      license
      B
      quality
      B
      maintenance
      Enables users to inspect and manage domains, DNS records (including A, AAAA, CNAME, MX, TXT and more), HTTP forwards, invoices and dynamic DNS through a hosting provider's API, with previewed change plans, conflict detection, backups and independent readback before writes. Offers DNS shortcuts such as website setup, verification records, bulk IP replacement, zone import/export and backup restore, exposed via local stdio or authenticated Streamable HTTP for a central gateway.
      27
      MIT
    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 8 tools

    Disambiguation4/5

    The specific tools (cf_verify, cf_list_zones, cf_dns_list/create/update/delete, cf_purge_cache) each target a distinct resource+action and are easy to tell apart. The only overlap is cf_request, a universal catch-all that can technically do anything the specific tools do, but the description explicitly frames it as a fallback, mitigating most ambiguity.

    Naming Consistency4/5

    All tools share the cf_ prefix and snake_case casing, which is clean and predictable. The pattern is mostly verb_noun (list_zones, purge_cache) but cf_dns_list is noun_verb while cf_dns_create/update/delete are noun_verb variants, a minor deviation rather than a real inconsistency.

    Tool Count5/5

    Eight tools is a well-scoped set: a small set of DNS CRUD operations, zone listing, cache purge, verification, and a universal escape hatch. Each tool earns its place without redundancy.

    Completeness4/5

    DNS record lifecycle is fully covered (list, create, update, delete) plus cache purge and token verification, with cf_request backfilling zone management and other endpoints. Only minor gaps exist (e.g. no explicit zone create/delete tool), but the universal tool makes these reachable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources