KeyCDN MCP. Control your global edge cache and content delivery.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
KeyCDN (Content Delivery Network) MCP Server gives your AI agent full control over global edge caching. Use it to purge specific URLs, invalidate entire zones, manage custom domain aliases, and pull new zones directly from your origin servers.
It also provides detailed traffic reports and lets you audit zone configurations without leaving your workflow.
What your AI agents can do
Add pull zone
Creates a new KeyCDN pull zone, connecting a new origin server to the global edge network.
Add zone alias
Adds a custom domain alias (CNAME) to an existing KeyCDN zone, mapping a branded URL to the content.
Delete zone
Removes a specific KeyCDN zone, revoking its wildcard subdomains and proxy connections.
You tell the agent to purge a URL or an entire zone, and it sends the invalidation request to KeyCDN.
You ask the agent to create, list, or delete entire zones, remapping your content delivery infrastructure.
You tell the agent to link a custom domain (like assets.company.com) to an existing zone, managing the necessary CNAME aliases.
You request a bandwidth report for a time period, and the agent retrieves consumption data to track your CDN spending.
You ask the agent for a zone's details, retrieving its configuration, TLS status, and caching rules.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
KeyCDN MCP Server: 10 Tools for CDN Control
Use these tools to programmatically manage every aspect of your content delivery network, from invalidating single files to setting up entire zones.
019d75c0add pull zone
Creates a new KeyCDN pull zone, connecting a new origin server to the global edge network.
019d75c0add zone alias
Adds a custom domain alias (CNAME) to an existing KeyCDN zone, mapping a branded URL to the content.
019d75c0delete zone
Removes a specific KeyCDN zone, revoking its wildcard subdomains and proxy connections.
019d75c0delete zone alias
Removes a custom domain alias from a KeyCDN zone.
019d75c0get zone
Retrieves the full configuration and details for one specific KeyCDN zone.
019d75c0list traffic reports
Retrieves a report listing bandwidth consumption for a specified time range.
019d75c0list zone aliases
Lists all custom domain aliases currently configured across all your KeyCDN zones.
019d75c0list zones
Returns a list of all active KeyCDN zones and their primary endpoints.
019d75c0purge specific url
Invalidates a single cached URL within a zone, avoiding a full purge.
019d75c0purge zone cache all
Clears the entire cache for a specified KeyCDN zone.
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 every 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 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
KeyCDN gives your AI agent full control over your global edge caching. You can use it to purge specific URLs, wipe out entire zones, manage custom domain aliases, and pull new zones straight from your origin servers. It also pulls detailed traffic reports and lets you check zone settings without leaving your workflow.
Purge Content Cache
You can tell your agent to purge a specific URL, and it invalidates that single cached file in a zone. If you need to wipe out everything, you can have it clear the entire cache for a whole zone. The agent also sends the invalidation request when you need to purge a single URL or an entire zone.
Manage Zone Endpoints
Your agent handles creating, listing, and deleting entire zones, letting you remap your content delivery infrastructure. You can use add_pull_zone to create a new KeyCDN pull zone, connecting a fresh origin server to the global edge network. You can also use list_zones to get a list of all active KeyCDN zones and their primary endpoints.
If a zone is retired, the agent uses delete_zone to remove it, revoking its wildcard subdomains and proxy connections.
Map Custom Domains
You can link a custom domain, like assets.company.com, to an existing zone by using add_zone_alias. This maps a branded URL to the content. You can also use list_zone_aliases to see all custom domain aliases set up across all your zones, and delete_zone_alias removes a specific custom domain alias from a zone.
Audit Traffic Usage
To track your CDN spending, you can ask the agent for a bandwidth report. list_traffic_reports pulls a report listing bandwidth consumption for a specified time range.
Inspect Zone Settings
If you need to see a zone's details, you can ask the agent to retrieve the full configuration for one specific zone using get_zone.
How KeyCDN MCP Works
- 1 1. Subscribe to the KeyCDN server and input your unique KeyCDN API Key.
- 2 2. Instruct your agent (Claude, Cursor, etc.) to perform a task, like 'list all my zones' or 'purge the cache for X'.
- 3 3. Your agent calls the appropriate tool, executes the action against KeyCDN, and returns the status or data.
The bottom line is that you manage your entire content delivery network from natural conversation, without touching the KeyCDN web interface.
Who Is KeyCDN MCP For?
This is for the DevOps Engineer who needs to manage content delivery at scale. It's for the Frontend Developer who needs to purge specific assets after a deployment. It’s for the Site Administrator who needs to audit global domain aliases across multiple production environments, all without switching tabs or logging into a separate dashboard.
Monitor CDN traffic patterns using list_traffic_reports and manage zone configurations across multiple production environments.
Run full cache invalidations (purge_zone_cache_all) or create new pull zones (add_pull_zone) directly from an agent prompt.
Verify asset delivery and purge specific URLs (purge_specific_url) immediately after pushing new code, right from their IDE.
Audit custom domain aliases (list_zone_aliases) and verify SSL/TLS statuses for global asset delivery efficiency.
What Changes When You Connect
- When you run
purge_specific_url, you don't have to purge the whole zone just because one CSS file changed. You hit the exact asset, keeping your cache clean and deployment fast. - Managing a new asset location is simple. Use
add_pull_zoneto connect a new origin server and immediately expand your content delivery network footprint. - If you need to rebrand or use a custom domain,
add_zone_aliaslets you map a branded URL to an existing zone without changing your underlying infrastructure. - You can track costs and usage by calling
list_traffic_reports. This shows you exactly how much bandwidth you're consuming, so you never get surprised by a bill. - Need to clean house?
delete_zonelets you instantly remove an entire zone and its associated proxy connections, giving you full cleanup control. - Audit your setup with
list_zone_aliasesandget_zone. These tools let you check every custom domain and zone setting without manually clicking through dozens of dashboard menus.
Real-World Use Cases
Hotfix Deployment: Need to bust cache for a CSS change.
A developer pushes a fix that changes app.css. Instead of asking a teammate to manually purge the zone, they ask their agent: 'Purge the cache for styles/app.css in zone 123.' The agent runs purge_specific_url, invalidating only the needed file and keeping the rest of the cache intact.
Expanding Global Footprint: Adding a new video stream.
The team needs to deliver video content from a new AWS bucket. They prompt their agent: 'Create a new pull zone for my video assets.' The agent runs add_pull_zone, connecting the new origin server and making the content available globally.
Domain Cleanup: Decommissioning an old staging site.
The staging environment is done. The administrator tells their agent: 'Delete the entire staging zone.' The agent runs delete_zone, instantly revoking all subdomains and proxy connections for that old content delivery endpoint.
Compliance Check: Verifying all custom endpoints.
The security team needs to verify that every custom domain alias is correctly configured. They prompt: 'List all custom domain aliases.' The agent runs list_zone_aliases, providing a definitive report of every mapped endpoint for audit purposes.
The Tradeoffs
Purging everything when only one file changed.
The user thinks: 'I'll just hit the big 'Purge All' button in the dashboard.' This forces a full cache purge (purge_zone_cache_all), which is slow, resource-intensive, and unnecessary if only one asset changed.
→
Instead, ask your agent to run purge_specific_url. This hits only the path that changed, keeping the rest of the zone's content cached and available immediately.
Ignoring domain aliases during migration.
A developer manually changes the asset endpoint in code, forgetting to update the domain mapping. The site breaks because the old custom domain alias points to nothing.
→
Before making changes, use list_zone_aliases to see all current mappings. Then, use add_zone_alias to set up the new, correct domain alias, ensuring your content remains accessible.
Relying on memory for infrastructure details.
A new team member has to remember which zone is live, which is staging, and what the current traffic volume is. They waste time clicking through multiple dashboards.
→
Start by running list_zones to see all active endpoints. Then, run list_traffic_reports to get the quantitative data on usage, keeping your audit trail in the chat.
When It Fits, When It Doesn't
Use this KeyCDN MCP Server if your workflow involves frequent, programmatic changes to your content delivery network. You need to manage the lifecycle of zones, aliases, and caches—not just consume them.
Don't use this if: You only need to view a simple report or check a single status. Use your native KeyCDN dashboard for simple viewing.
Use this if: You need to trigger actions—like invalidating a specific URL (purge_specific_url), setting up a new zone (add_pull_zone), or verifying domain mappings (add_zone_alias). The value here is the ability to execute these actions and audit the state using tools like get_zone or list_zone_aliases all through your agent, maintaining a single, auditable conversation log.
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 INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Cache invalidation shouldn't require a full zone purge.
Right now, if you update a single CSS file, you often have to go into the CDN dashboard and hit a 'Purge Everything' button. That's slow, costly, and overkill. You're making the whole global cache unavailable just because one asset changed.
With the KeyCDN MCP Server, you just tell your agent, 'Purge the cache for `styles/app.css`.' The agent runs `purge_specific_url`, invalidating only that one file globally. The rest of your cached assets stay put, keeping your deployment cycle fast and efficient.
KeyCDN MCP Server: Manage Zones and Aliases
Setting up a new content endpoint or updating a domain alias usually means logging into the CDN, finding the right zone, and manually adding a CNAME record. This is tedious and prone to human error.
Now, you tell your agent, 'Add the custom domain `assets.company.com` to the main zone.' The agent runs `add_zone_alias`, updating the necessary infrastructure details and confirming the alias in one step. It keeps your workflow moving without leaving your IDE.
Common Questions About KeyCDN MCP
How do I list all my KeyCDN zones using the list_zones tool? +
You ask your agent to 'list all zones.' The agent runs list_zones and returns a list of all active endpoints and their immutable names. This is the first step in auditing your entire content delivery setup.
Is `purge_specific_url` the same as `purge_zone_cache_all`? +
No. purge_specific_url targets a single file path (e.g., /app.css) within a zone. purge_zone_cache_all clears the entire cache for that zone. Use the specific purge if you only changed one asset.
What if I need to add a new content source to my CDN? +
You use the add_pull_zone tool. This tool creates a new zone and connects your specified origin server, instantly making the content available through KeyCDN's global edge locations.
Can I check my CDN traffic usage using list_traffic_reports? +
Yes. You tell your agent the time period, and it runs list_traffic_reports. This gives you consumption data, helping you monitor your spending and usage patterns.
How do I verify all my custom domain aliases using list_zone_aliases? +
Use list_zone_aliases. This tool aggregates and displays every custom domain alias mapped across all your zones, which is critical for security and compliance audits.
How do I add a custom domain alias using the add_zone_alias tool? +
You use add_zone_alias to map a custom domain (like assets.mycompany.com) to an existing KeyCDN zone. This requires you to update the corresponding DNS CNAME records for the alias to work.
Can I delete a specific KeyCDN zone using the delete_zone tool? +
Yes, delete_zone instantly revokes wildcard subdomains and drops proxy connections for that zone. Be careful, as this action is permanent and cannot be undone.
How do I manage cache invalidation for a single file using purge_specific_url? +
purge_specific_url sends a purge request for a single file path, like /app.css, without invalidating the entire zone. This is ideal for targeted updates.
Can I purge the entire cache for a specific zone using my agent? +
Yes. Use the purge_zone_cache_all tool with your Zone ID. Your agent will instantly trigger a global invalidation across all Edge servers, forcing KeyCDN to re-fetch all assets from your origin upon the next request.
How do I invalidate a single file instead of purging the whole zone? +
The purge_specific_url tool allows for granular cache invalidation. You just need to provide the Zone ID and the absolute URL of the resource (e.g. your CDN subdomain + path) to clear that specific file from the edge nodes.
Can my agent check how much traffic I've used this month? +
Absolutely. Use the list_traffic_reports tool and provide a start and end timestamp. Your agent will retrieve the bandwidth consumption analytics for your account, helping you track CDN usage and spending in real-time.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Smithery
AI MCP registry: discover, search, and connect MCP servers to your agents via Smithery.
Clever Cloud (Developer PaaS API)
Manage your Clever Cloud infrastructure—apps, add-ons, and deployments—directly from your AI agent.
Make (Workflow Automation)
Manage workflow automation via Make — audit scenarios, track execution logs, and monitor data stores.
You might also like
Zoho Books
Manage invoices, estimates, and contacts via the Zoho Books API.
Hexomatic
Automate web scraping and worklfows via Hexomatic — manage workflows, recipes, and automation logs directly from any AI agent.
Tubular
Analyze social video performance across YouTube, Facebook, and TikTok with audience insights and competitive benchmarking.