Get the FREE Ultimate OpenClaw Setup Guide →

cloudflare-api-key-automation

Scanned
npx machina-cli add skill ComposioHQ/awesome-claude-skills/cloudflare-api-key-automation --openclaw
Files (1)
SKILL.md
3.0 KB

Cloudflare API Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/cloudflare_api_key

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Cloudflare API connection via RUBE_MANAGE_CONNECTIONS with toolkit cloudflare_api_key
  • 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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit cloudflare_api_key
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. 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 API 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 API task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["cloudflare_api_key"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Cloudflare API-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit cloudflare_api_key
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_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-api-key-automation/SKILL.mdView on GitHub

Overview

Automate Cloudflare API operations via Composio's Cloudflare API toolkit using Rube MCP. Start by discovering current tool schemas with RUBE_SEARCH_TOOLS, then connect to Cloudflare and execute the discovered tools in a controlled workflow.

How This Skill Works

The skill uses Rube MCP to discover available Cloudflare API tools, validates an ACTIVE Cloudflare connection via RUBE_MANAGE_CONNECTIONS with the cloudflare_api_key toolkit, and then runs the chosen tool with RUBE_MULTI_EXECUTE_TOOL. Tool schemas are fetched fresh each run to prevent hardcoding.

When to Use It

  • You need to orchestrate Cloudflare API tasks with up-to-date tool schemas.
  • You are setting up a new Cloudflare connection and must verify ACTIVE before automation.
  • You want to discover available Cloudflare tools and their input schemas programmatically.
  • You need to execute a discovered tool with proper memory and session management in a workflow.
  • You must handle paginated responses when listing or querying Cloudflare resources.

Quick Start

  1. Step 1: Add the MCP server at https://rube.app/mcp in your client config.
  2. Step 2: Run RUBE_SEARCH_TOOLS to fetch current Cloudflare tool schemas.
  3. Step 3: Use RUBE_MANAGE_CONNECTIONS with toolkit 'cloudflare_api_key' and run RUBE_MULTI_EXECUTE_TOOL on a discovered tool.

Best Practices

  • Always call RUBE_SEARCH_TOOLS before executing to fetch current tool schemas.
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
  • Use exact field names and types from live schemas; avoid hardcoding slugs.
  • Include memory (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls.
  • Reuse session IDs within a workflow and manage pagination tokens as needed.

Example Use Cases

  • Create or update a DNS record for a domain using the discovered DNS tool.
  • Purge Cloudflare cache for a list of URLs via the purge tool.
  • Update or add firewall rules for a zone through the firewall tool.
  • List all DNS records across multiple zones while handling pagination.
  • Rotate API tokens or credentials via the Cloudflare API toolkit after establishing a connection.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers