Can my AI agent instantly purge a CDN Pull Zone after a release?

Yes. Instead of logging into the admin portal manually, just tell your agent you deployed the frontend. It will grab the ID of your main Pull Zone and blast the purge_pull_zone command immediately.

Does it track new files uploaded directly to my Storage Zone?

Yes! Provide the API password and string path, and the agent lists precise object files inside the folder natively. E-commerce sites use this to verify if static images successfully pushed to the edge before updating database paths.

Can it provision new Pull Zones from scratch?

Absolutely. You can request a fresh caching domain, pass the target origin URL (like an S3 bucket), and the AI builds your CDN layer generating the specific `*.b-cdn.net` URL response for you.

Bunny.net MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Bunny.net
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Bunny.net through Vinkius, pass the Edge URL in the `mcps` parameter and every Bunny.net tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Bunny.net Specialist",
    goal="Help users interact with Bunny.net effectively",
    backstory=(
        "You are an expert at leveraging Bunny.net tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Bunny.net "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Bunny.net MCP Server

Connect your Bunny.net platform to any AI agent and operate your edge CDN and cloud storage entirely through natural conversation.

When paired with CrewAI, Bunny.net becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Bunny.net tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Pull Zones Management — View and create ultra-fast reverse proxy acceleration links that distribute your media globally
Cache Invalidations — Instantly purge the cache on specific CDN zones, pushing out immediate changes and breaking TTLs
Edge Storage Clusters — Analyze or delete raw origin volumes routing permanent data arrays
File Exploration — Inspect precise static payloads directly inside the CDN Edge Storage structure via FTP parameters

The Bunny.net MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Bunny.net to CrewAI via MCP

Follow these steps to integrate the Bunny.net MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Bunny.net

Why Use CrewAI with the Bunny.net MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Bunny.net through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Bunny.net + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Bunny.net MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Bunny.net for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Bunny.net, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Bunny.net tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Bunny.net against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Bunny.net MCP Tools for CrewAI (10)

These 10 tools become available when you connect Bunny.net to CrewAI via MCP:

add_pull_zone

Returns the new Pull Zone ID and default b-cdn.net domain. Provision a radically fast new CDN reverse proxy domain

add_storage_zone

Defaults to explicit NY regional primary datacenters. Bootstrap an entirely empty replication Volume inside Bunny.net

delete_pull_zone

Instantly invalidates assigned `b-cdn.net` aliases dropping incoming proxy connections out of the Anycast caching tree entirely. Destroy an active CDN acceleration mapping terminating global traffic

delete_storage_zone

Requires zone to be empty or forces recursive wipes freeing the namespace back into the registry. Vaporize an existing Bunny CDN Storage Zone entirely

get_pull_zone

Exposes enabled SSL configurations, Bandwidth limits, and advanced Edge Rules intercepting requests. Perform structural extraction of metadata for one specific Pull Zone

get_storage_zone

Returns FTP access credentials, read-only vs read-write keys, and origin PoPs. Inspect deep internal credentials identifying a precise Storage Zone

list_files

Requires the specific Zone FTP/API Password. Returns literal byte lengths and cryptographic hash footprints. Enumerate explicitly uploaded binary assets nested strictly inside Storage

list_pull_zones

Returns pull zone IDs, names, hostnames, and origin URL targets. Identify global Bunny CDN accelerated delivery domains (Pull Zones)

list_storage_zones

Locate physical Edge Storage origin folders managed natively on Bunny

purge_pull_zone

Spikes Origin ingress traffic rapidly pulling entirely fresh payload structures. Blast an immediate Cache Invalidation forcing origin asset re-fetching

Example Prompts for Bunny.net in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Bunny.net immediately.

"List all my current Pull Zones and their original targets."

"My site design looks old, the JS didn't update. Purge Pull Zone ID 12040 right now."

"What files are currently inside the '/assets/' path of our 'main-storage-x' Edge Storage zone?"

Troubleshooting Bunny.net MCP Server with CrewAI

Common issues when connecting Bunny.net to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Bunny.net + CrewAI FAQ

Common questions about integrating Bunny.net MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.