Skip to main content
Glama
itunified-io

mcp-cloudflare

by itunified-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-cloudflare

No user-submitted related servers found.

    Related Servers

    • mcp-opnsense

      itunified-io
      A
      license
      A
      quality
      D
      maintenance
      Slim OPNsense MCP Server — 62 tools for managing firewall infrastructure via the OPNsense REST API. Covers DNS/Unbound, Firewall rules, Diagnostics, Interfaces, DHCP (ISC + Kea), System/Backups, ACME/Let's Encrypt, and Firmware. No SSH, no shell, API-only with 3 runtime dependencies. AGPL-3.0 + Commercial dual-licensed.
      100
      54 npm
      2
      AGPL 3.0

    • cloudflare-dns-mcp-server

      piersdd
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A token-efficient MCP server for managing Cloudflare DNS zones and records with full CRUD support and bulk operations. It can be deployed locally via stdio or as a Cloudflare Worker for remote HTTP access.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 95 tools

    Disambiguation3/5

    Most tools are clearly scoped by resource (dns, tunnel, kv, r2, zt, worker). However, there is notable overlap: cloudflare_zone_setting_get vs cloudflare_security_level_get (security_level is a zone setting), and cloudflare_security_insights vs cloudflare_security_insights_severity_count add nearly redundant tools. The WAF and IP access rule tools could also be confused.

    Naming Consistency5/5

    All tools follow a consistent resource_noun_verb or resource_noun_action pattern (e.g., cloudflare_dns_list, cloudflare_r2_bucket_create). The naming clearly groups by service area and action, making it predictable across the large surface.

    Tool Count2/5

    95 tools is extremely high for a coherent MCP server. While Cloudflare has many products, this set spans zones, DNS, WAF, tunnels, Zero Trust, Workers, KV, R2, analytics, and security — far too broad. An agent would struggle to discover and choose among 95 tools.

    Completeness4/5

    The core resources (DNS, KV, R2, Workers, Zero Trust, WAF) have solid lifecycle coverage — create/read/update/delete operations are present. Some gaps exist (no DNS bulk operations, no WAF ruleset update, no R2 object upload), but most workflows can be completed.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources