Skip to main content
Glama
daniil-shumko

Cloudflare Workers MCP Server

by daniil-shumko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Cloudflare Workers MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      19 npm
      MIT

    • Cloudflare MCP Server

      ry-ops
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      13
      2
      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.
      -

    • Cloudflare MCP Server

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      Manage Cloudflare resources such as Workers, KV, R2, D1, Durable Objects, and more using natural language via the Model Context Protocol.
      1,282 npm
      Apache 2.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

    A4.2/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources/actions, but there is potential confusion between deploy_worker, create_version, create_deployment, and rollback_worker since they all relate to deployment lifecycle. Similarly, get_worker, get_worker_code, and get_version could be mixed up, though descriptions clarify the differences.

    Naming Consistency4/5

    The naming pattern is largely consistent verb_noun (e.g., deploy_worker, list_versions, set_cron_triggers). Minor deviations include health_check (a noun phrase) and set_workers_dev (unusual phrasing), but these do not undermine overall predictability.

    Tool Count4/5

    With 22 tools, the server is slightly heavy but still well-scoped for the breadth of Cloudflare Workers functionality. Each tool covers a distinct aspect, though a few could be consolidated (e.g., deployment-related commands) to reduce count.

    Completeness5/5

    The tool surface is comprehensive, covering Worker CRUD, version/deployment management, domain attachments, cron triggers, logs, settings, and static site deployment. No significant gaps are apparent for typical Workers workflows.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources