What is cloudflare-automation?

A Composio-based workflow that automates Cloudflare tasks via Rube MCP, using live tool schemas.

How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing any workflow to fetch the latest tool slugs and input schemas.

What if the Cloudflare connection is not ACTIVE?

Follow the returned auth link from RUBE_MANAGE_CONNECTIONS to complete setup, then re-check for ACTIVE before running tools.

cloudflare-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/cloudflare-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Cloudflare Automation via Rube MCP

Automate Cloudflare operations through Composio's Cloudflare toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/cloudflare

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Cloudflare connection via RUBE_MANAGE_CONNECTIONS with toolkit cloudflare
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit cloudflare
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Cloudflare operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Cloudflare task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["cloudflare"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Cloudflare-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/cloudflare-automation/SKILL.mdView on GitHub

Overview

Automate Cloudflare operations through Composio’s Cloudflare toolkit via Rube MCP. It guides you to discover current tool schemas, connect to Cloudflare, and execute tools safely. This reduces manual steps and keeps workflows aligned with live tool definitions.

How This Skill Works

Use RUBE_SEARCH_TOOLS to discover compatible Cloudflare tools and their input schemas, then verify your Cloudflare connection with RUBE_MANAGE_CONNECTIONS and an ACTIVE status. Finally, run tools through RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id for continuity.

When to Use It

You need to automate routine Cloudflare tasks from Composio.
You must run with the latest tool schemas before execution.
You want to verify the Cloudflare connection is ACTIVE before workflows.
You want to discover available Cloudflare tools and their inputs first.
You’re performing multiple tools in a single session with proper memory handling.

Quick Start

Step 1: Get Rube MCP configured by adding the rube MCP endpoint to your client.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Cloudflare tool schemas and available tools.
Step 3: Manage Cloudflare connection and execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from tool schemas; avoid hardcoding.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and manage pagination when needed.

Example Use Cases

Update a DNS A record for a domain using a discovered tool slug and its input schema.
Purge Cloudflare cache for a list of URLs across zones in a single workflow.
Create or modify a firewall rule using the tool’s required arguments.
Rotate TLS/SSL settings across multiple Cloudflare zones via a single session.
Bulk apply DNS changes and cache purges in a reusable session with memory handling.

Frequently Asked Questions

Add this skill to your agents