KeyCDN MCP. Control global asset caching and delivery from chat.
Manage your global content delivery network (CDN) directly through conversation. This MCP lets you purge specific cached URLs or entire zones, create new pull zones for origin servers, and monitor detailed traffic bandwidth reports without logging into a web dashboard.
Give Claude and any AI agent real-world access
Target and clear the cache for a single file URL in a zone, avoiding the need to purge everything.
Instantly wipe the entire cache for an assigned KeyCDN zone when content changes globally.
Create and configure new pull zones, connecting your origin servers directly to KeyCDN's global network points.
Bind or unbind custom domain names (CNAMEs) to existing zones, maintaining branded asset delivery URLs.
Retrieve zone configuration details, list all active zones, or permanently delete entire acceleration zones.
Ask an AI about this
Waiting for input…
What AI agents can do with KeyCDN (Content Delivery Network) with 10 Tools
Use these tools to perform every CDN operation imaginable—from adding a new content source via `add_pull_zone` to monitoring traffic reports.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using KeyCDN (Content Delivery Network) MCPAdd Zone Alias
Attaches a custom domain name to an existing KeyCDN zone, allowing you to use your own branded URL for assets.
Add Pull Zone
Creates and sets up a new pull zone, which points KeyCDN's global network back to...
Delete Zone Alias
Removes a custom domain name alias from a specific KeyCDN zone when you change...
Delete Zone
Completely removes an entire, dedicated KeyCDN zone and all its associated wildcard...
Get Zone
Retrieves detailed configuration information for one specific KeyCDN zone.
List Zone Aliases
Lists all custom domain aliases currently bound across every zone in your account.
List Traffic Reports
Generates and retrieves detailed reports showing how much bandwidth was consumed over a given time period.
List Zones
Returns an immutable list of all existing KeyCDN zones and their primary endpoints.
Purge Specific Url
Invalidates a single file URL within a zone, letting you clear only the necessary...
Purge Zone Cache All
Wipes out the entire content cache for a specified KeyCDN zone at once.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with KeyCDN (Content Delivery Network), then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by KeyCDN. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The headache of stale content
Right now, when a developer pushes updated styles or images, they have to remember to jump into the CDN provider's dashboard. They find the zone, locate the asset path, and manually trigger an invalidation for every single file that changed. If there are hundreds of assets, this process takes minutes of tedious clicking, and it’s easy to miss one.
With this MCP, you tell your agent what needs fixing—'Purge all cache for the new logo images.' The agent handles the complex calls through tools like `purge_specific_url` or `purge_zone_cache_all`. You get instant confirmation that the content is invalidated globally, and you don't have to touch a dashboard.
Control Zone Configuration with KeyCDN MCP
Normally, setting up custom domain aliases or adding new pull zones requires navigating deep into the platform console. You must find the right section and input the CNAME records manually before you can point traffic to the correct origin server.
Now, your agent handles it. Simply ask your AI client to 'add a custom alias for staging' or 'create a pull zone for our API.' The MCP executes `add_zone_alias` or `add_pull_zone`, making complex infrastructure changes happen with simple conversation.
What KeyCDN MCP does for your AI
Need to update an image on your site and make sure the old version doesn't show up anywhere? Forget jumping between developer consoles. This MCP connects your content delivery infrastructure to your AI agent, giving you full control over your global edge caching from natural conversation. You can instantly purge a zone's entire cache or target just one file URL, ensuring fresh assets hit your users immediately.
It handles everything from setting up new pull zones to managing custom domain aliases for branded URLs. For monitoring, you can retrieve detailed bandwidth consumption reports over any time period. When you connect this MCP via Vinkius, your agent gains the authority needed to perform complex infrastructure tasks—like inspecting caching rules or deleting entire acceleration zones—all while staying within your preferred AI client.
019d75c0-9ab4-70f4-a309-d96697448bd8 How to set up KeyCDN MCP
The bottom line is that you control complex CDN operations using simple natural language prompts instead of navigating multiple web forms.
Subscribe to this MCP and provide your unique KeyCDN API key.
Connect the credentials to any compatible AI client (like Cursor or VS Code).
Ask your agent to perform an action, like listing all zones or purging a specific URL.
Who uses KeyCDN MCP
This MCP is for the site administrator who can't afford downtime because a single stale asset breaks the checkout flow, or the SRE who needs to audit global zone configurations across dozens of environments in minutes.
Needs to monitor bandwidth usage and use list_traffic_reports to verify if a recent code deployment caused an unexpected traffic spike or cost increase.
Must run purge_specific_url immediately after pushing new CSS files, ensuring the cache doesn't serve outdated styles and breaking the UI.
Uses this MCP to check zone health with get_zone or set up a new content source using add_pull_zone, making deployment processes faster and safer.
Benefits of connecting KeyCDN MCP
Save time on cache invalidation. Instead of manually purging every single URL, use purge_specific_url to hit only the files that changed after a code deployment.
Gain full visibility into spending. Run list_traffic_reports to pull bandwidth consumption data and track CDN costs without opening a billing dashboard.
Manage branded assets easily. Use add_zone_alias to map custom domains, keeping your URLs clean while still using the global CDN network.
Scale infrastructure with confidence. Need a new content source? Run add_pull_zone directly through your agent instead of navigating multiple console tabs.
Audit zone health on demand. Use list_zones and get_zone to quickly verify that all required endpoints are active and configured correctly across environments.
KeyCDN MCP use cases
The Broken Image Fix
A frontend dev notices a user is seeing an old logo image after deployment. They ask their agent to run purge_specific_url on the asset's path, instantly resolving the stale content issue without impacting other assets.
The Quarterly Budget Check
An SRE needs to justify CDN spend to a manager. They ask their agent to run list_traffic_reports for the last quarter, getting precise bandwidth data instantly for review.
Multi-Site Rollout
A DevOps engineer is setting up a new client site and needs a dedicated content source. They use add_pull_zone to connect the site's origin servers, completing the setup in one conversation.
The Site Cleanup
An administrator confirms that an old testing zone is no longer needed. They ask their agent to run delete_zone, ensuring all associated assets and subdomains are revoked instantly.
KeyCDN MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Deleting the entire zone
When a specific asset fails, a developer might panic and try to delete the whole zone just to 'clear' it.
Don't delete the zone. Use purge_specific_url for targeted invalidation, or run purge_zone_cache_all if you must clear everything.
Manual DNS checks
Manually logging into a separate DNS panel to verify a custom domain alias is pointing correctly.
Use the MCP's tools like list_zone_aliases and add_zone_alias to manage mappings directly, verifying status through natural conversation.
Ignoring traffic reports
Assuming usage is normal because nothing broke immediately after a major launch.
Always run list_traffic_reports before and after high-impact deployments to baseline expected bandwidth consumption.
When to use KeyCDN MCP
Use this MCP if your primary need is direct, operational control over the CDN's cache layer and infrastructure state. You should use it when you absolutely must purge assets or check zone status without a GUI login. Don't use this if you only need general website monitoring; for that, dedicated performance tools are better. Crucially, don't try to use it for writing code or generating content—it is purely an infrastructure control plane tool. If your goal is simply to view assets, check the zone status using get_zone; if your goal is to change them, you need a purge command like purge_specific_url.
Frequently asked questions about KeyCDN MCP
How do I list all my zones using the KeyCDN MCP? +
You run the list_zones tool. This immediately returns a complete, updated list of every active zone endpoint associated with your account.
Can I purge only one file in KeyCDN using this MCP? +
Yes. Use purge_specific_url. This is much better than running a full cache purge because it limits the invalidation to just the single asset path you specify.
What if my custom domain alias stops working with KeyCDN MCP? +
You can check all configured aliases using list_zone_aliases. If necessary, you can remove a broken link using delete_zone_alias.
Is the KeyCDN MCP safe for deleting zones? +
Yes, but be careful. The delete_zone tool permanently removes an entire zone and all its associated assets. Always confirm the name before executing this action.