What can you do with the Cloudflare integration?

LiveContext exposes 59 operations on Cloudflare, covering key, namespace, bucket and database. Common uses include Resource cleanup, Disaster recovery and Capacity planning.

LiveContext

All integrations

Cloudflare integration

Enterprise-grade CDN, DDoS protection, and web security platform API. Manage DNS zones and records, configure caching, firewall rules, SSL certificates, and Workers. Includes D1 serverless SQLite databases, KV key-value storage, R2 object storage with zero egress fees, and Workers edge computing platform.

59 toolsTokenAPI docs

Connect Cloudflare How integrations work

Common Cloudflare use cases

Resource cleanup
Disaster recovery
Capacity planning
Clean up test storage
Create edge middleware
Decommission services
Audit storage resources
Validate before operations
URL redirects
Data migration

What you can do with Cloudflare

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Key, 6 operations

DELETEbulk_delete_keys
Deletes multiple keys in a single batch request.
PUTbulk_write_keys
Writes multiple key-value pairs in a single batch request.
DELETEdelete_key
Deletes a key from a KV namespace.
GETget_key
Reads the value of a key from a KV namespace.
GETlist_keys
Lists all keys in a KV namespace with optional filtering.
PUTwrite_key
Writes a key-value pair to a KV namespace with optional expiration.

Namespace, 5 operations

POSTcreate_namespace
Creates a new KV namespace for key-value storage.
DELETEdelete_namespace
Permanently deletes a KV namespace and all its data.
GETget_namespace
Retrieves details of a specific KV namespace.
GETlist_namespaces
Lists all KV namespaces in the Cloudflare account.
PUTrename_namespace
Renames a KV namespace without affecting its data.

Bucket, 4 operations

POSTcreate_bucket
Creates a new R2 storage bucket with optional location hint.
DELETEdelete_bucket
Deletes an empty R2 storage bucket permanently.
GETget_bucket
Retrieves details of a specific R2 storage bucket.
GETlist_buckets
Lists all R2 storage buckets in the Cloudflare account.

Database, 4 operations

POSTcreate_database
Creates a new D1 SQLite database with optional location hint.
DELETEdelete_database
Permanently deletes a D1 database and all its data.
GETget_database
Retrieves details of a specific D1 database.
GETlist_databases
Lists all D1 SQLite databases in the Cloudflare account.

Dns record, 4 operations

POSTcreate_dns_record
Creates a new DNS record in a Cloudflare zone.
DELETEdelete_dns_record
Deletes a DNS record from a Cloudflare zone.
GETlist_dns_records
Lists all DNS records for a Cloudflare zone with filtering options.
PATCHupdate_dns_record
Updates an existing DNS record in a Cloudflare zone.

Firewall rule, 4 operations

POSTcreate_firewall_rule
Creates a new firewall rule with custom expression to control traffic access.
DELETEdelete_firewall_rule
Deletes a firewall rule from the zone. The rule stops being enforced immediately.
GETlist_firewall_rules
Lists all firewall rules configured for a Cloudflare zone.
PUTupdate_firewall_rule
Updates an existing firewall rule's expression, action, or configuration.

Worker, 4 operations

DELETEdelete_worker
Deletes a Worker script from Cloudflare's edge network.
GETget_worker
Downloads the source code of a specific Worker script.
GETlist_workers
Lists all Cloudflare Workers scripts in the account for edge computing.
PUTupload_worker
Deploys a new Worker script or updates an existing one at Cloudflare's edge.

Zone, 4 operations

POSTcreate_zone
Creates a new zone (domain) in your Cloudflare account for DNS and CDN management.
DELETEdelete_zone
Deletes a zone from Cloudflare, removing all DNS records and configuration.
GETget_zone
Retrieves detailed configuration for a specific Cloudflare zone.
GETlist_zones
Lists all zones (domains) in the Cloudflare account with filtering and pagination.

Bucket cors, 3 operations

DELETEdelete_bucket_cors
Removes all CORS rules from an R2 bucket.
PUTenable_bucket_cors
Configures CORS rules for browser access to an R2 bucket.
GETget_bucket_cors
Retrieves CORS configuration for an R2 bucket.

Page rule, 3 operations

POSTcreate_page_rule
Creates a page rule for URL-specific behaviors like redirects and caching.
DELETEdelete_page_rule
Deletes a page rule from the zone. URL-specific behaviors stop immediately.
GETlist_page_rules
Lists all page rules for URL-based behavior configuration.

Worker route, 3 operations

POSTcreate_worker_route
Creates a route to trigger a Worker for matching URL patterns.
DELETEdelete_worker_route
Deletes a Worker route from the zone.
GETlist_worker_routes
Lists all Worker routes configured for a zone.

Backup, 2 operations

GETlist_database_backups
Retrieves the current or nearest bookmark for D1 Time Travel recovery.
POSTrestore_database_backup
Restores a D1 database to a previous point in time using Time Travel.

Query, 2 operations

POSTquery_database
Executes SQL queries against a D1 database with optional parameters.
POSTraw_query
Executes raw SQL with detailed execution statistics.

R2 token, 2 operations

POSTcreate_r2_token
Creates S3-compatible API credentials for R2 access.
GETlist_r2_tokens
Lists all R2 API tokens in the account.

Worker setting, 2 operations

GETget_worker_settings
Retrieves settings and bindings for a Worker script.
PATCHupdate_worker_settings
Updates settings and bindings for a Worker script.

Analytics, 1 operation

GETget_zone_analytics
Retrieves analytics dashboard data for a Cloudflare zone.

Bucket usage, 1 operation

GETget_bucket_usage
Retrieves storage usage statistics for an R2 bucket.

Cache, 1 operation

POSTpurge_cache
Purges cached content from Cloudflare's CDN edge servers.

Database export, 1 operation

POSTexport_database
Exports a D1 database to a SQL dump file for backup.

Database import, 1 operation

POSTimport_database
Imports SQL statements into a D1 database for migrations or restoration.

Ssl, 1 operation

GETget_ssl_settings
Retrieves SSL/TLS configuration for a zone including encryption mode and certificate status.

Worker analytics, 1 operation

GETget_worker_usage
Retrieves aggregated usage analytics for Worker scripts.

Cloudflare API rate limits

1,200 requests per 5-minute window per user. See https://developers.cloudflare.com/fundamentals/api/reference/limits/

These are the limits Cloudflare documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Cloudflare documentation for current values.

Use Cloudflare from Claude Code, Cursor or Codex

Connect Cloudflare in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Cloudflare operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Cloudflare

Create your workspace
Sign up free. Nothing to install.
Connect Cloudflare once
Add your Cloudflare connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Cloudflare integration FAQ

What can you do with the Cloudflare integration?: LiveContext exposes 59 operations on Cloudflare, covering key, namespace, bucket and database. Common uses include Resource cleanup, Disaster recovery and Capacity planning.
What are the Cloudflare API rate limits?: 1,200 requests per 5-minute window per user. See https://developers.cloudflare.com/fundamentals/api/reference/limits/ Limits are set by Cloudflare and can depend on your plan.