2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 10 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add KeyCDN (Content Delivery Network) as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="keycdn_content_delivery_network_agent",
            tools=tools,
            system_message=(
                "You help users with KeyCDN (Content Delivery Network). "
                "10 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())
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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use KeyCDN (Content Delivery Network) tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

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

01

Install AutoGen

Run pip install "autogen-ext[mcp]"

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

04

Explore tools

The workbench discovers 10 tools from KeyCDN (Content Delivery Network) automatically

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

AutoGen provides unique advantages when paired with KeyCDN (Content Delivery Network) through the Model Context Protocol.

01

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use KeyCDN (Content Delivery Network) tools to solve complex tasks

02

Role-based architecture lets you assign KeyCDN (Content Delivery Network) tool access to specific agents. a data analyst queries while a reviewer validates

03

Human-in-the-loop support: agents can pause for human approval before executing sensitive KeyCDN (Content Delivery Network) tool calls

04

Code execution sandbox: AutoGen agents can write and run code that processes KeyCDN (Content Delivery Network) tool responses in an isolated environment

KeyCDN (Content Delivery Network) + AutoGen Use Cases

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

01

Collaborative analysis: one agent queries KeyCDN (Content Delivery Network) while another validates results and a third generates the final report

02

Automated review pipelines: a researcher agent fetches data from KeyCDN (Content Delivery Network), a critic agent evaluates quality, and a writer produces the output

03

Interactive planning: agents negotiate task allocation using KeyCDN (Content Delivery Network) data to make informed decisions about resource distribution

04

Code generation with live data: an AutoGen coder agent writes scripts that process KeyCDN (Content Delivery Network) responses in a sandboxed execution environment

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

These 10 tools become available when you connect KeyCDN (Content Delivery Network) to AutoGen 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 AutoGen

Ready-to-use prompts you can give your AutoGen 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 AutoGen

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

01

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

KeyCDN (Content Delivery Network) + AutoGen FAQ

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

01

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call KeyCDN (Content Delivery Network) tools during their conversation turns.
02

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
03

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

Connect KeyCDN (Content Delivery Network) to AutoGen

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