
Cloudflare Api Key Automation
- 7 installs
- 71.8k repo stars
- Updated July 24, 2026
- composiohq/awesome-claude-skills
Automate Cloudflare tasks with API-key auth from an agent by connecting through Composio's cloudflare_api_key toolkit over the Rube MCP server.
About
Automates Cloudflare operations using an API-key auth flow through Composio's cloudflare_api_key toolkit over the Rube MCP endpoint. A developer uses it to manage Cloudflare resources from an agent after connecting and discovering tool schemas.
- Runs Cloudflare API Key operations through Composio's cloudflare_api_key toolkit via Rube MCP
- Discovers tool schemas with RUBE_SEARCH_TOOLS before executing
Cloudflare Api Key Automation by the numbers
- 7 all-time installs (skills.sh)
- Ranked #1,587 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/composiohq/awesome-claude-skills --skill cloudflare-api-key-automationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 7 |
|---|---|
| repo stars | ★ 71.8k |
| Last updated | July 24, 2026 |
| Repository | composiohq/awesome-claude-skills ↗ |
What it does
Automate Cloudflare tasks with API-key auth from an agent by connecting through Composio's cloudflare_api_key toolkit over the Rube MCP server.
Files
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_CONNECTIONSwith toolkitcloudflare_api_key - Always call
RUBE_SEARCH_TOOLSfirst 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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 API-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit cloudflare_api_key |
| 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](https://composio.dev)