Cloudflare gives Wrangler and MCP users optional OAuth scopes

Cloudflare has moved OAuth consent for two developer-facing tools toward least privilege. Wrangler and the Cloudflare API MCP server now let users edit optional permissions during authorization instead of approving every optional scope requested by the client. Required scopes remain selected.

The change matters most for teams giving command-line tools or agents access to cloud accounts. A narrower grant can reduce the damage from an over-permissioned integration or a compromised token, while still allowing a workflow to request more access when a command genuinely needs it.

What changed in Cloudflare OAuth

Cloudflare’s August 20 general-availability announcement lets OAuth client developers classify configured scopes as required or optional. The consent flow includes permission search and Read Only and Full Access templates. Users can turn optional permissions off before authorizing an application.

Cloudflare’s August 22 Wrangler and API MCP changelog applies the model to the tools developers are likely to use from terminals and AI-assisted workflows. During wrangler login or MCP authorization, users can choose specific permissions rather than accepting the complete optional set.

This is a permission change, not a new authentication protocol. The client still receives the scopes that were granted, and required permissions cannot be removed from the consent screen.

Why it matters for MCP and agent workflows

MCP servers and developer CLIs can combine many operations behind one interface. That makes broad authorization convenient, but it also makes it harder to see whether a tool needs read access, deployment rights, account administration, or some combination. Optional scopes put that decision in the authorization flow where the user can inspect it.

The practical trade-off is friction. If a command or tool call needs a scope that was declined, Cloudflare says the client must be reauthorized with that permission. Teams should therefore define separate profiles for read-only inspection, deployment, and administrative work rather than granting Full Access by default.

What developers should check

Review existing Wrangler and API MCP authorizations instead of assuming the new dialog automatically narrows old grants. Confirm which permissions are required by each workflow, and test a declined optional scope in a non-production account so failures are visible before a deployment depends on it.

Cloudflare’s Wrangler documentation also notes that OAuth credentials are stored in a plaintext TOML file by default unless the keyring option is enabled. Scope reduction limits authorization, but it does not remove the need to protect the local credential store or to use API tokens for non-interactive CI/CD flows where appropriate.

Evidence

Cloudflare’s product changelog documents the GA optional-scope model, while the tool-specific changelog confirms the rollout for Wrangler and the Cloudflare API MCP server. Independent technical coverage describes the shift from all-or-nothing consent to task-based permission selection. The remaining operational question is how teams will split scopes across real agent workflows without turning every missing permission into a manual reauthorization step.