2,500+ MCP servers ready to use
Vinkius

KeyCDN (Content Delivery Network) MCP Server for CrewAI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="KeyCDN (Content Delivery Network) Specialist",
    goal="Help users interact with KeyCDN (Content Delivery Network) effectively",
    backstory=(
        "You are an expert at leveraging KeyCDN (Content Delivery Network) 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 KeyCDN (Content Delivery Network) "
        "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)
KeyCDN (Content Delivery Network)
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 KeyCDN (Content Delivery Network) MCP Server

Connect your KeyCDN account to any AI agent and take full control of your global edge caching and content delivery infrastructure through natural conversation.

When paired with CrewAI, KeyCDN (Content Delivery Network) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call KeyCDN (Content Delivery Network) 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

  • Cache Orchestration — Purge the entire cache for a zone or perform granular invalidations for specific file URLs to ensure fresh content delivery instantly
  • Zone Management — Create and configure new Pull Zones to connect your origin servers to KeyCDN's global edge locations directly from your agent
  • Custom Domain Aliases — Bind and manage custom domain mappings (CNAMEs) to existing zones to maintain branded asset delivery URLs securely
  • Traffic Analytics — Retrieve detailed bandwidth consumption reports over specific time periods to monitor your CDN spending and usage patterns
  • Origin Audit — Inspect detailed caching rules, TLS settings, and origin server configurations assigned to your active zones
  • Infrastructure Control — Enable, disable, or permanently delete distributed acceleration zones to manage your content delivery pipeline in real-time

The KeyCDN (Content Delivery Network) 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 KeyCDN (Content Delivery Network) to CrewAI via MCP

Follow these steps to integrate the KeyCDN (Content Delivery Network) MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from KeyCDN (Content Delivery Network)

Why Use CrewAI with the KeyCDN (Content Delivery Network) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with KeyCDN (Content Delivery Network) through the Model Context Protocol.

01

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

02

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

03

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

04

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

KeyCDN (Content Delivery Network) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the KeyCDN (Content Delivery Network) MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries KeyCDN (Content Delivery Network) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries KeyCDN (Content Delivery Network), analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain KeyCDN (Content Delivery Network) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries KeyCDN (Content Delivery Network) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

KeyCDN (Content Delivery Network) MCP Tools for CrewAI (10)

These 10 tools become available when you connect KeyCDN (Content Delivery Network) to CrewAI via MCP:

01

add_pull_zone

Create a new KeyCDN pull zone

02

add_zone_alias

g. assets.company.com) to an existing KeyCDN zone. DNS CNAME records should be updated accordingly. Add a custom domain alias to a KeyCDN zone

03

delete_zone

Instantly revokes wildcard subdomains and drops proxy connections natively. Delete a specific KeyCDN zone

04

delete_zone_alias

Delete a custom domain alias from a KeyCDN zone

05

get_zone

Get details for a specific KeyCDN zone

06

list_traffic_reports

List traffic bandwidth consumption reports

07

list_zone_aliases

List custom domain aliases for all zones

08

list_zones

Returns immutable `.kxcdn.com` endpoints and zone configurations. List all KeyCDN zones

09

purge_specific_url

g., `/app.css`), avoiding a full zone cache purge. Purge a specific cached URL in a KeyCDN zone

10

purge_zone_cache_all

Purge the entire cache for a KeyCDN zone

Example Prompts for KeyCDN (Content Delivery Network) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with KeyCDN (Content Delivery Network) immediately.

01

"List all my KeyCDN zones"

02

"Purge the cache for this URL in zone 123: https://main-123.kxcdn.com/styles/app.css"

03

"How much traffic did we use in the last 7 days?"

Troubleshooting KeyCDN (Content Delivery Network) MCP Server with CrewAI

Common issues when connecting KeyCDN (Content Delivery Network) to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

KeyCDN (Content Delivery Network) + CrewAI FAQ

Common questions about integrating KeyCDN (Content Delivery Network) MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect KeyCDN (Content Delivery Network) to CrewAI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.