Cloudflare CLI now in beta
Cloudflare's new command-line interface (cf) is now available in beta, providing a unified tool to manage zones, DNS, storage, security settings, and to create, develop, and deploy Workers projects without switching between tools. It supports over 2,900 API commands, Wrangler migration, and agent-friendly search functionality.
The Cloudflare CLI, cf, is now in beta. cf is one command-line interface for the public Cloudflare API and for Workers projects. Use it to manage zones, DNS, storage, and security settings, and to create, develop, and deploy Workers, without switching between tools.
Install cf globally, then sign in:
npm install --global cfyarn global add cfpnpm add --global cfbun add --global cf
cf auth login
With cf, you can:
- Manage resources across Cloudflare. More than 2,900 commands cover the public Cloudflare API, and most print their results as JSON.
- Create and deploy Workers.
cf initcreates a project that usescloudflare.config.ts, a typed configuration file.cf dev,cf build, andcf deploydevelop, build, and deploy it. - Move from Wrangler.
cf migrateconverts a Wrangler configuration file tocloudflare.config.ts. You can also runcfresource commands in an existing Wrangler project without migrating it. - Work with coding agents.
cf cli searchfinds the command for a task from a plain-language description, so an agent can find and run commands without prior knowledge ofcf.
cf is in beta. Commands, configuration, and Build Output can change before the stable release.
To get started, refer to Install and sign in. To move an existing project, refer to Migrate a Wrangler project.
Source: original entry ↗
More from Cloudflare
Follow Cloudflare to get its new changes in your feed and email digest.
Cloudflare API MCP server now serves Cloudflare skills
The Cloudflare API MCP server now integrates with the Skills over MCP extension, allowing MCP clients to discover and access Cloudflare skills. Users can add the MCP server endpoint to compatible MCP clients to access these skills.
WAF failed detections field now available in Rules
A new cf.appsec.request.failed_detections field lets you control how rules handle requests when security detections fail. This array of detection IDs covers content scanning, WAF attack scoring, attack signatures, leaked credentials, and AI-based PII/prompt injection/custom topic detection failures, and works across custom rules, rate limiting rules, and request header transform rules.
Markdown for Agents: More efficient in-process streaming conversion
Markdown for Agents now uses an in-process streaming engine at the edge to convert HTML, reducing overhead and memory use. The conversion limit increased from 2 MiB to 6 MiB, and token count headers are no longer generated.