cloudflare-tools
Related Servers
Alternatives to cloudflare-tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with the Cloudflare REST API for managing DNS records, zones, and other Cloudflare resources.MIT
- AlicenseCqualityAmaintenanceEnables AI agents to inspect and manage Cloudflare zones through 29 tools covering DNS records, cache purges, zone settings, Rulesets, Worker metadata and read-only analytics. Read operations run freely while every mutation, such as a DNS edit or batch apply, stays behind explicit per-operation preview and confirmation with private, least-privilege token profiles.2932 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Cloudflare DNS records, including listing zones and records, and creating, updating, or deleting DNS records.23 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to inspect Cloudflare accounts and zones, manage DNS records, purge cached content, and inventory Worker scripts, KV namespaces, and R2 buckets through the Cloudflare API.MIT
- AlicenseBqualityDmaintenanceExposes Cloudflare DNS, security, redirects and zone-settings functionality as structured tools that AI assistants like Claude Desktop can invoke directly.1823 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to manage Cloudflare resources through natural language, including DNS records, zone management, Workers KV storage, cache purging, and analytics. Supports comprehensive Cloudflare operations with secure API token authentication.132MIT
TDQS
Scored across 8 tools
Tools are largely distinct: cache_purge vs cache_purge_all are explicitly cross-referenced, and dnssec_enable/disable are clearly separated from the read-only dnssec status in zone_read. The only real risk is setting_edit vs setting_weaken, which requires the agent to know whether a change lowers protection — though setting_edit safely refuses such changes and points to weaken.
Every tool follows the same cloudflare_<resource>_<action> snake_case pattern, with consistent prefixes for zone-scoped operations. Minor suffixes like _all and _enable/_disable fit the same convention without breaking it.
Eight tools is well within the ideal range and each maps to a distinct, non-redundant operation on accounts or zones. Nothing feels padded or missing at the count level.
Zone settings, cache purge, and DNSSEC are covered read+write, but DNS record management (list/create/update/delete) — arguably the core of Cloudflare zone work — is absent, as is any zone creation/deletion. Agents will hit a dead end for common DNS-record tasks.