Can I use Cloudflare as a CLI?

Yes. KosmoKrator exposes a Cloudflare CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Cloudflare through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Cloudflare tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Cloudflare credentials stored?

Cloudflare credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Cloudflare MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

cloud

Cloudflare CLI for Coding Agents

Use the Cloudflare CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit Cloudflare feedback View package source

Cloudflare CLI for Coding Agents

Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

Use this pattern when another coding agent needs exact commands and schema discovery. The Cloudflare CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Cloudflare CLI for Coding Agents
kosmokrator integrations:configure cloudflare --set access_token="$CLOUDFLARE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call cloudflare.cloudflare_list_zones '{"name":"example_name","status":"example_status","page":1,"per_page":1}' --json

Discovery Before Execution

Agents and scripts can inspect Cloudflare docs and schemas before choosing a function.

kosmo integrations:docs cloudflare --json
kosmo integrations:docs cloudflare.cloudflare_list_zones --json
kosmo integrations:schema cloudflare.cloudflare_list_zones --json
kosmo integrations:search "Cloudflare" --json
kosmo integrations:list --json

Useful Cloudflare CLI Functions

Function	Type	Parameters	Description
`cloudflare.cloudflare_list_zones`	Read	name, status, page, per_page	List all Cloudflare zones (domains). Returns zone IDs, names, status, and plan info. Use this to discover zone identifiers needed for DNS and analytics operations.
`cloudflare.cloudflare_get_zone`	Read	zone_id	Get detailed information about a specific Cloudflare zone, including its ID, name, status, nameservers, and plan.
`cloudflare.cloudflare_list_dns_records`	Read	zone_id, type, name, content, page, per_page	List DNS records for a Cloudflare zone. Returns record IDs, types, names, content, TTL, and proxy status.
`cloudflare.cloudflare_create_dns_record`	Write	zone_id, type, name, content, ttl, proxied	Create a new DNS record in a Cloudflare zone. Supports A, AAAA, CNAME, MX, TXT, NS, SRV, and other record types.
`cloudflare.cloudflare_list_page_rules`	Read	zone_id, status, page, per_page	List page rules for a Cloudflare zone. Returns rule IDs, targets, actions, and priority.
`cloudflare.cloudflare_get_analytics`	Read	zone_id, since, until, continuous	Get analytics dashboard data for a Cloudflare zone. Returns HTTP requests, bandwidth, threats, and pageview metrics over a time range.
`cloudflare.cloudflare_get_current_user`	Read	none	Get details of the currently authenticated Cloudflare user. Returns user ID, email, username, and account info.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Cloudflare CLI Pages

CI Cloudflare CLI for CI. Cron Jobs Cloudflare CLI for cron jobs. Shell Scripts Cloudflare CLI for shell scripts. Headless Automation Cloudflare CLI for headless automation.