Generated banner for Cf CLI
Generated logo for Cf CLI

Cf CLI

CloudflareOfficialPublished by Cloudflare

  • Skill
  • Tool integration
  • Cloud and DevOps
  • Apache-2.0
  • Low risk

From the author

Cloudflare's official cf CLI (beta) for the public Cloudflare API and Workers projects. Use for finding and running Cloudflare commands from the terminal — sign-in and profiles, cf cli search, cf schema, cf deploy/dev/build, resource commands for DNS, zones, D1, KV, and R2 — and for choosing between cf and Wrangler in a project.
— the description by Cloudflare

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The cf-cli is the official command-line tool for interacting with the Cloudflare API and managing Workers projects. It provides a unified interface for tasks ranging from authentication and account management to resource operations like DNS, D1, KV, and R2. Designed for both interactive terminal use and automated environments, it features a search-based command discovery system and supports schema-based API requests. The tool is currently in beta and emphasizes safe execution through dry-run capabilities and explicit configuration management.

What it does

  • Provides a searchable interface for over 2,900 Cloudflare API commands.
  • Manages authentication, user profiles, and API token configuration.
  • Handles the full lifecycle of Workers projects including init, development, and deployment.
  • Performs CRUD operations on Cloudflare resources like DNS, Zones, D1, KV, and R2.
  • Supports schema inspection to verify API request structures before execution.
  • Offers safe execution modes including dry-runs and non-interactive error handling.

When to use it

  • When you need to manage Cloudflare resources directly from the terminal.
  • When starting a new Workers project that does not require legacy Wrangler configuration.
  • When you need to look up specific API command syntax or request parameters.
  • When integrating Cloudflare operations into CI/CD pipelines using API tokens.
  • When migrating existing projects from Wrangler to the newer cf configuration format.

Advantages

  • Direct access to the comprehensive public Cloudflare API.
  • Built-in search functionality helps discover commands without memorizing documentation.
  • Schema-based validation ensures correct API request formatting.
  • Dry-run mode prevents accidental changes to production infrastructure.
  • Supports unattended authentication for automated CI environments.

Usage examples

“cf cli search create a DNS record”
The CLI returns a list of matching commands and their usage, allowing you to identify the correct syntax for creating a DNS record.
“cf schema d1 create”
Displays the required API request shape, including the method, path, and necessary body fields for creating a D1 database.
“cf deploy --dry-run”
Prints the JSON request that would be sent to the Cloudflare API without actually deploying the project, ensuring the configuration is correct.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/cloudflare/cf-cli/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip cf-cli.zip -d .agents/skills

Documentation by Cloudflare

Cloudflare CLI (cf)

cf is Cloudflare's command-line interface for the public Cloudflare API (2,900+ commands, most generated from API schemas) and for Workers projects. It is in beta: commands, configuration, and Build Output can change before the stable release.

Prefer retrieval over pre-trained knowledge. Describe the task to cf cli search, inspect the match with cf schema or --help, and preview with --dry-run before running a command you have not verified.

Docs index: https://developers.cloudflare.com/cf/llms.txt

Documentation

TopicPage
Install, sign in, credential and account selectionhttps://developers.cloudflare.com/cf/get-started/index.md
First Worker with cf init, cf dev, cf deployhttps://developers.cloudflare.com/cf/get-started/first-worker/index.md
Find, create, and delete resources from the terminalhttps://developers.cloudflare.com/cf/get-started/resources/index.md
cf for Wrangler usershttps://developers.cloudflare.com/cf/wrangler/index.md
Migrate a Wrangler project with cf migratehttps://developers.cloudflare.com/cf/wrangler/migrate/index.md
Wrangler-to-cf command and config referencehttps://developers.cloudflare.com/cf/wrangler/reference/index.md
Develop, build, and deploy; modes and previewshttps://developers.cloudflare.com/cf/projects/index.md
Typed cloudflare.config.tshttps://developers.cloudflare.com/cf/projects/cloudflare-config/index.md
Using cf with coding agents (safety rules)https://developers.cloudflare.com/cf/agents/index.md
CI, API tokens, unattended authenticationhttps://developers.cloudflare.com/cf/ci/index.md
Environment variableshttps://developers.cloudflare.com/cf/environment-variables/index.md
Find slow or expensive D1 databases and queries with cf sql queryhttps://developers.cloudflare.com/d1/observability/find-expensive-queries/index.md

FIRST: check installation and sign in

npm install --global cf   # installs two equivalent commands: `cf` and `cloudflare`
cf --version
cf auth whoami
  • Requires Node.js 22.18 or later. Bun is not supported.

  • If another tool named cf is on your PATH, use cloudflare instead — the package installs both commands.

  • cf auth login prints a link and a one-time code, then opens the browser. On a remote machine, over SSH, or in a container, add --no-browser so cf only prints the link; approve it from another device. Add --force to sign in again.

  • cf keeps its own credentials and does not reuse a Wrangler login.

  • Unattended agents and CI cannot complete cf auth login — set CLOUDFLARE_API_TOKEN instead (see https://developers.cloudflare.com/cf/ci/index.md).

To make agents prefer cf, add this to the user-level AGENTS.md, CLAUDE.md, or equivalent:

When interacting with Cloudflare, use the `cf` CLI unless the project has a
Wrangler configuration file.

Find commands

cf cli search "create a DNS record"   # local, no credentials; quote the whole task; up to 5 JSON matches
cf schema d1 create                   # API request shape: method, path, params, body fields
cf <command> --help                   # arguments and options (e.g. cf deploy --help)

cf cli search takes the task as one argument — unquoted words after the first are parsed as unknown commands. cf schema covers generated API commands; for command arguments and options use --help.

Read output

  • Results are JSON on standard output; status messages and errors go to standard error, so piping to jq or redirecting needs no extra flags.

  • Lists print one JSON array page; paging options differ per command — check --help.

  • A failed command exits non-zero and prints the error to standard error.

Run commands safely

  • Preview first. --dry-run prints the request as JSON without sending it, and needs no credentials.

  • Aborted deletes still exit 0. In a non-interactive session, a destructive command without --force prints Aborted. to standard error and exits 0 — a zero exit does not mean the resource was deleted.

  • Review --force before allowing it. On some commands --force is also an API parameter (for example, cf workers delete --force also deletes a Worker that other Workers reference).

  • --local is limited. It works for KV keys, D1 databases (cf d1 raw, cf d1 migrations list|apply), and R2 objects; other commands (including cf d1 query) return an error instead of calling the API.

Choose the CLI for this project

  • cloudflare.config.ts exists: use cf.

  • wrangler.jsonc, wrangler.json, or wrangler.toml exists, and no cloudflare.config.ts: keep Wrangler for dev, build, and deploy. Do not run cf dev, cf build, or cf deploy there — they can generate a new configuration that ignores the Wrangler file, or fail. cf resource commands (DNS, zones, storage) are fine alongside it. Run cf migrate only when the user asks, and follow Migrate a Wrangler project: preview with cf migrate --dry-run, run cf migrate, then resolve the TODO(@cloudflare) comments in the generated cloudflare.config.ts.

  • Neither exists: use cf, as Use cf with coding agents recommends. Do not install Wrangler or create a Wrangler configuration file.

Product documentation often shows only Wrangler commands and wrangler.jsonc configuration. In a cf project, treat those as tasks to translate, not commands to run, and do not add a Wrangler configuration file. Use one CLI per project; the only exceptions are the commands under Commands cf does not support yet. For Wrangler equivalents, use the Wrangler to cf reference or cf cli search. Do not translate Wrangler commands from memory. For the full comparison, refer to cf for Wrangler users.

Commands cf does not support yet

cf does not support every Wrangler command yet. Run these with npx wrangler instead of adding Wrangler to the project. Wrangler does not read cloudflare.config.ts, so pass the Worker name:

  • Live logs: npx wrangler tail <WORKER_NAME>.

  • A single secret: npx wrangler secret put <SECRET_NAME> --name <WORKER_NAME>. Or upload secrets with a new Worker version by passing --secrets-file <PATH> to cf deploy or cf workers versions create.

For the current list, refer to "Commands not yet supported" in the Wrangler to cf reference.

Skill feedback

If the user reports that this skill gave incorrect or outdated guidance, or is missing information, read references/skill-feedback.md.

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

What our scanner noticed· Low risk

  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Cloudflare
Publisher
Cloudflare (Official)
Source
cloudflare/skills · skills/cf-cli · commit 6eb6c78
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Cloudflare or Cloudflare.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download cf-cli.zip