Configuration

Accounts#

Open Settings → Tools → Cloudflare, or add an account from the Toolkit for Cloudflare tool window. Use API-token or OAuth authentication and select the intended account in the explorer. Grant permissions for the services you actually use.

Local development#

Keep wrangler.toml, wrangler.json, or wrangler.jsonc in the project and use the project’s Wrangler version. The Local Dev view discovers supported bindings and local state. A local binding is distinct from its remote resource even when the names match.

Resource panels#

Select a resource in the explorer before opening SQL, logs, traces, deployment history, or storage views. Requests stay associated with the panel’s original account; opening another account does not turn an existing panel into that account’s resource.

MCP and status#

Configure MCP servers with the required connection and authentication options before browsing tools. Inspect a tool’s arguments and target account before invoking operations. Status panels and incident notifications reflect Cloudflare platform information, rather than the health of every individual application.