Building a CLI for all of Cloudflare

The nutshell

Cloudflare is rebuilding Wrangler into a single, unified CLI it hopes will cover its entire product surface. It has been reported that the company now exposes the full API in a single Code Mode MCP server that uses fewer than 1,000 tokens — a striking efficiency claim. Today you can try the technical preview by running npx cf or installing npm install -g cf; for now it only covers a subset of products, but the roadmap is ambitious: CLI commands for every Cloudflare product, plus integrated infrastructure-as-code workflows.

The engineering pivot

The crux of the change is tooling, not just a new command set. Cloudflare says OpenAPI wasn’t expressive enough for everything they wanted — interactive CLI flows, local dev bindings for Workers, agent skills, and richer config semantics. So they designed a TypeScript-first schema system that can describe APIs, CLI arguments, and runtime context in one place, and still emit OpenAPI when needed. In other words: spec-as-code. It’s a pragmatic nod to a trend we’ve seen across the industry — TypeScript as the lingua franca of modern platform tooling — and it promises less manual stitching between SDKs, docs, and the CLI.

Why it matters

Developers — and increasingly software agents — prefer CLIs. They script them, they feed them to AI assistants, they automate them into pipelines. Cloudflare’s bet is that by generating consistent interfaces from a single schema, they’ll ship commands faster and avoid the “one-off” product islands that frustrate teams today. There’s genuine excitement here: the emotional core is simple — developers want predictability and a small, coherent surface to learn. Will this reduce friction? Probably. Will it create new challenges around schema governance and vendor-specific conventions? That’s the rub.

The next play

This is an early, public play; Cloudflare says they’ll continue iterating in the open to tune ergonomics for both humans and agents. Feedback is the point — they want developers to try cf, poke at the generated commands, and tell them what’s awkward. Expect a slow, deliberate expansion over the coming months as Wrangler’s familiar features are folded back in. So ask yourself: what happens when every API is also a command on your terminal? For many teams, that’s the moment their cloud tooling finally starts to feel like one coherent product.

Sources: cloudflare.com, Hacker News