cloudflare-api-key-automation

通过 Rube MCP 自动执行 Cloudflare API 任务并辅助查询最新接口结构。

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "cloudflare-api-key-automation" 技能：
1. 下载 https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/cloudflare-api-key-automation/SKILL.md
2. 保存为 ~/.claude/skills/cloudflare-api-key-automation/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

批量管理 DNS 记录

输入

先搜索 Cloudflare 相关工具与最新参数结构，然后列出可用的 DNS 管理操作。接着为我的 zone 批量新增 10 条 A 记录，并返回执行结果摘要与失败项。

预期产出

先展示已发现的工具和参数结构，再输出 DNS 记录创建结果、成功失败统计及错误说明。

更新防火墙或安全配置

输入

先搜索当前 Cloudflare 安全相关工具和输入 schema。然后帮我检查可用的防火墙或访问控制操作，并按最佳实践更新指定站点的一项安全规则，最后生成变更说明。

预期产出

返回可用安全操作清单、执行的配置变更、影响范围以及简明的变更记录。

查询并执行区域配置操作

输入

先搜索 Cloudflare zone 相关工具，确认最新 schema 与必填字段。然后告诉我可读取和可修改的区域配置项，并执行一个配置更新示例，附带回滚建议。

预期产出

输出当前可用的 zone 操作、所需参数、一次配置更新结果，以及相应的回滚建议。

// 文档

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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit cloudflare_api_key
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 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

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`