executor-cloudflare

Configures and operates Cloudflare services through Executor integrations and OAuth connections.

Updated Oct 15, 2019
One-click install
npx skills add https://github.com/kkkaoru/dotfiles --skill executor-cloudflare-kkkaoru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executor-cloudflare
Source: https://github.com/kkkaoru/dotfiles/tree/main/.agents/skills-stroage/executor-cloudflare
Command: npx skills add https://github.com/kkkaoru/dotfiles --skill executor-cloudflare-kkkaoru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing Cloudflare accounts, Workers, R2, D1, and billing through scattered MCP configurations and ad-hoc credentials is error-prone. This Skill centralizes all Cloudflare access through Executor as the single integration, credential, and policy manager, avoiding duplicate MCP registrations across agents. ## Core Features & Use Cases - Executor-based integration routing: Discovers and calls registered Cloudflare MCP integrations (API, docs, bindings, builds, observability, GraphQL) instead of configuring direct MCP connections in each agent. - OAuth and API-token setup: Guides human-in-the-loop OAuth flows and credential handoffs through Executor's browser UI, keeping secrets out of chat, shell arguments, and logs. - R2 object operations via OAuth: Uses the existing authorized connection for bucket and object read/write/delete through REST routes discovered in Code Mode, without issuing new S3 credentials. - Billing investigation workflow: Aggregates Billable Usage API data inside Code Mode, separates fixed subscription fees from measured usage, and reports provisional subtotals with explicit uncertainty. - Use Case: A user asks why their Cloudflare bill changed. The Skill verifies the token-authenticated connection, fetches billable-usage for the current cycle, aggregates ContractedCost by service family and currency, and reports confirmed charges versus estimates. ## Quick Start Set up Cloudflare through Executor and verify my account connection with a read-only API call.

Frequently Asked Questions about executor-cloudflare

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Cloudflare MCP through Executor?

Fetch the official Cloudflare agent-setup prompt, inventory existing Executor integrations, then register only missing services using official HTTPS endpoints via executor.mcp.addServer. Finish with a bounded read-only live call such as listing accounts to verify the connection.

How do I access R2 objects without S3 credentials?

Use the existing OAuth connection through the cloudflare-api Code Mode execute tool, calling REST routes like GET/PUT/DELETE /accounts/{account_id}/r2/buckets/{bucket}/objects/{key}. Probe with a non-secret object, verify exact read-back content, and clean up afterward.

Why does my Cloudflare OAuth connection lack billing access?

An OAuth connection that lists accounts may still lack Billing Read permission, and reauthorization cannot add scopes the MCP does not publish. Check granted scopes against the official scope catalog, or add a separate API-token-authenticated connection to the same MCP endpoint.

How do I calculate current Cloudflare billing cycle charges?

Use the Billable Usage API: check billable-usage/info for coverage and cycle anchor, then fetch billable-usage without dates for the current period. Sum ContractedCost per record grouped by currency and service family inside Code Mode, never summing the running-total CumulatedContractedCost column.

Can I use API tokens instead of OAuth for Cloudflare MCP?

Yes, the official Cloudflare API MCP supports Bearer API-token authentication on the same endpoint. Create the token through Executor's connections.createHandoff so the user enters the secret in the browser UI, scoped to the target account with minimum read permissions.

What are the limitations of Cloudflare MCP billing data?

Billable Usage shows accrued usage overage charges only, not fixed subscriptions, taxes, credits, or final invoices. Results may lag real time, interval ends are exclusive, and empty rows do not prove zero charges unless coverage and dataset semantics are verified.