home / skills / composiohq / awesome-claude-skills / bunnycdn-automation

bunnycdn-automation skill

safe

/bunnycdn-automation

This skill automates Bunnycdn tasks via Composio's Rube MCP, discovering current tool schemas and managing connections for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill bunnycdn-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: bunnycdn-automation
description: "Automate Bunnycdn tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Bunnycdn Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/bunnycdn](https://composio.dev/toolkits/bunnycdn)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bunnycdn connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bunnycdn`
- 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 `bunnycdn`
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: "Bunnycdn 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 Bunnycdn task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["bunnycdn"]
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 Bunnycdn-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bunnycdn` |
| 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)*

Overview

This skill automates BunnyCDN tasks through Composio’s Bunnycdn toolkit via the Rube MCP. It standardizes discovery, connection checks, and execution steps so agents run CDN operations reliably. The workflow emphasizes always querying tools first to avoid schema drift and ensures connection status before any action.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover available Bunnycdn tool slugs and their input schemas, RUBE_MANAGE_CONNECTIONS to verify or establish an active Bunnycdn connection, and RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH) to run one or more toolkit tools. It enforces schema compliance, session reuse, and includes memory in execution calls to match MCP requirements.

When to use it

Automating BunnyCDN cache purges, zone or pull zone updates, and content operations.
Running repeatable bulk operations across many zones or assets.
Embedding BunnyCDN tasks into larger Composio/Rube MCP workflows.
When tool schemas may change or when multiple executions require consistent sessions.
When you need to programmatically verify connection status before actions.

Best practices

Always call RUBE_SEARCH_TOOLS first — do not hardcode tool slugs or arguments.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the bunnycdn toolkit before executing tools.
Use the exact field names and types returned by the tool search results to avoid schema errors.
Always include a memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse session IDs across a single workflow; generate new IDs for distinct workflows.
Check responses for pagination tokens and fetch until complete for list operations.

Example use cases

Discover available BunnyCDN purge and zone-management tools, then purge multiple caching zones in a single RUBE_MULTI_EXECUTE_TOOL call.
Validate and complete BunnyCDN authentication flow via RUBE_MANAGE_CONNECTIONS, following any returned auth links until ACTIVE.
List all pull zones using paginated results from discovered tools and iterate through tokens to collect every item.
Run bulk configuration updates across zones using RUBE_REMOTE_WORKBENCH and run_composio_tool() for parallel operations.

FAQ

Do I need API keys to connect to Rube MCP?

No API keys are required for the MCP endpoint; add https://rube.app/mcp to your client as an MCP server to connect.

What should I do if a tool schema changes?

Always call RUBE_SEARCH_TOOLS before executing. Update your arguments to match the returned schema fields and types from the search response.