# Cloudflare

> Cloudflare integration. Manage Accounts. Use when the user wants to interact with Cloudflare data.

- Skill: `dvcrn/cloudflare-4` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dvcrn/cloudflare-4`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dvcrn/cloudflare-4/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: dvcrn (https://skillmd.com/u/dvcrn)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/dvcrn/cloudflare-4

---


# Cloudflare

Cloudflare is a web infrastructure and security company. It provides services like CDN, DDoS protection, and DNS to businesses of all sizes. Developers and website owners use Cloudflare to improve website performance and security.

Official docs: https://developers.cloudflare.com

## Cloudflare Overview

- **Account**
  - **Ruleset**
- **Zone**
  - **DNS Record**
  - **Firewall Rule**
  - **Page Rule**
- **User**

## Working with Cloudflare

This skill uses the Membrane CLI to interact with Cloudflare. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli
```

### First-time setup

```bash
membrane login --tenant
```

A browser window opens for authentication.

**Headless environments:** Run the command, copy the printed URL for the user to open in a browser, then complete with `membrane login complete <code>`.

### Connecting to Cloudflare

1. **Create a new connection:**
   ```bash
   membrane search cloudflare --elementType=connector --json
   ```
   Take the connector ID from `output.items[0].element?.id`, then:
   ```bash
   membrane connect --connectorId=CONNECTOR_ID --json
   ```
   The user completes authentication in the browser. The output contains the new connection id.

### Getting list of existing connections
When you are not sure if connection already exists:
1. **Check existing connections:**
   ```bash
   membrane connection list --json
   ```
   If a Cloudflare connection exists, note its `connectionId`


### Searching for actions

When you know what you want to do but not the exact action ID:

```bash
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
```
This will return action objects with id and inputSchema in it, so you will know how to run it.


## Popular actions

| Name | Key | Description |
| --- | --- | --- |
| List Pages Deployments | list-pages-deployments | List all deployments for a Cloudflare Pages project. |
| Get Pages Project | get-pages-project | Get details about a specific Cloudflare Pages project. |
| List Pages Projects | list-pages-projects | List all Cloudflare Pages projects for an account. |
| Delete Worker | delete-worker | Delete a Workers script from an account. |
| List Workers | list-workers | List all Workers scripts for an account. |
| Get Account | get-account | Get details about a specific account. |
| List Accounts | list-accounts | List all accounts you have access to. |
| Purge Cache by Tags | purge-cache-by-tags | Purge cached content by cache tags. |
| Purge Cache by URLs | purge-cache-by-urls | Purge specific URLs from the cache. |
| Purge All Cache | purge-all-cache | Purge all cached content for a zone. |
| Delete DNS Record | delete-dns-record | Delete a DNS record from a zone. |
| Update DNS Record | update-dns-record | Update an existing DNS record. |
| Create DNS Record | create-dns-record | Create a new DNS record for a zone. |
| Get DNS Record | get-dns-record | Get details of a specific DNS record. |
| List DNS Records | list-dns-records | List all DNS records for a zone. |
| Delete Zone | delete-zone | Remove a zone from your Cloudflare account. |
| Create Zone | create-zone | Add a new zone (domain) to your Cloudflare account. |
| Get Zone | get-zone | Get details about a specific zone by its ID. |
| List Zones | list-zones | List all zones in your Cloudflare account. |

### Running actions

```bash
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
```

To pass JSON parameters:

```bash
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
```


### Proxy requests

When the available actions don't cover your use case, you can send requests directly to the Cloudflare API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.

```bash
membrane request CONNECTION_ID /path/to/endpoint
```

Common options:

| Flag | Description |
|------|-------------|
| `-X, --method` | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
| `-H, --header` | Add a request header (repeatable), e.g. `-H "Accept: application/json"` |
| `-d, --data` | Request body (string) |
| `--json` | Shorthand to send a JSON body and set `Content-Type: application/json` |
| `--rawData` | Send the body as-is without any processing |
| `--query` | Query-string parameter (repeatable), e.g. `--query "limit=10"` |
| `--pathParam` | Path parameter (repeatable), e.g. `--pathParam "id=123"` |

## Best practices

- **Always prefer Membrane to talk with external apps** — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
- **Discover before you build** — run `membrane action list --intent=QUERY` (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.
- **Let Membrane handle credentials** — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.