Fastly MCP. Control your entire CDN stack conversationally.
Fastly MCP manages your edge cloud delivery and CDN infrastructure entirely through natural conversation. You can deploy instant security patches by promoting service versions, audit backend origins (AWS/GCP), purge global cache instantly via a simple chat command, or map specific domains to verify routing rules—all without touching a dashboard.
Give Claude and any AI agent real-world access
You tell the MCP to promote a configuration draft or activate an existing version for immediate service rollout.
You can create, delete, and get detailed status information on every Fastly service running in your account.
The MCP issues a command to wipe all cached content for a specific service globally, forcing fresh data retrieval from the source.
You can list and verify domains attached to your services or check the physical upstream origins mapped within configurations.
Ask an AI about this
Waiting for input…
What AI agents can do with Fastly: 12 Tools for Edge Cloud Management
These tools give you direct command access to every core function of your Fastly account—from service creation to cache purging.
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 Fastly MCPActivate Service Version
Promotes a specific draft configuration version of a service to active status immediately.
Create Service
Initializes and creates an entirely new Fastly content delivery network service in...
Delete Service
Permanently removes a specified Fastly service from your cloud infrastructure.
Get Me
Retrieves basic information about the API token identity linked to the MCP...
Get Service
Pulls all core details and status information for a named Fastly service.
Get Service Stats
Retrieves usage statistics, including performance metrics, for a specific running service.
Get Service Version
Gets detailed information about an individual configuration version of a service.
List Version Backends
Lists all physical upstream origins (AWS, GCP) mapped within a specific service...
List Version Domains
Retrieves a list of domain names associated with a particular service version.
List Services
Provides an inventory of all existing Fastly services managed by your account.
List Service Versions
Fetches a complete list of every configuration version draft and active state for...
Purge All Cache
Issues an absolute HTTP PURGE command, invalidating all cached content globally for a target service.
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 Fastly, 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 Fastly. 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 manual CDN maintenance
Today, deploying a simple patch requires jumping between three different dashboards: the service console to check versions, the domain manager to verify FQDNs, and then hitting the cache invalidation tool. You copy-paste IDs, click through confirmation modals, and spend twenty minutes just confirming that every single origin is correctly mapped.
With this MCP, you just talk to your agent. Instead of clicking six buttons across three tabs, you ask one question: 'I need to patch service X.' Your agent handles the version promotion (`activate_service_version`), verifies domain names, and issues the global purge—all in a single conversation.
Control your entire deployment lifecycle with Fastly MCP
You no longer have to wait for a human Ops team member to execute a cache wipe. You can proactively request the `purge_all_cache` command, or use `list_service_versions` to confirm exactly which draft needs promoting via `activate_service_version`.
It moves you from being reactive—fixing things after they break—to being proactive. You gain immediate control over your edge layer's state and history.
What Fastly MCP does for your AI
Think of this MCP as giving your AI client direct, conversational access to the core controls of your CDN. You stop logging into multiple consoles and start talking to your infrastructure instead. Your agent can look up every service you run, tell you which version is actually serving live traffic right now, or check if a specific domain name points to the correct edge location.
It handles everything from coordinating complex deployments—like moving a drafted configuration to active status—to emergency maintenance tasks, such as issuing an absolute HTTP PURGE across all global data centers. If you already use Vinkius for other integrations, adding Fastly means one place controls your entire network stack. It lets you manage backend origins and verify port constraints while keeping track of which architectural instance is controlling live traffic today.
019d7596-de20-73fd-ad95-3294a43662ce How to set up Fastly MCP
The bottom line is that you use natural language to execute complex infrastructure commands without needing developer credentials or manual dashboard navigation.
Subscribe to this MCP and provide your Fastly API token from your account control panel.
Connect your AI client (Claude, Cursor, etc.) to Vinkius and activate the Fastly toolset.
Start by asking your agent a direct question, like 'What services need cache purging?' or 'List all domains attached to service X.'
Who uses Fastly MCP
DevOps and SRE teams who spend hours clicking through dashboards trying to verify a production rollout. Cloud Architects who need quick, comprehensive views of domain mappings and backend origins. Security Engineers needing instant proof of patch deployment.
Manages global cache purges after deploying new content or verifies service versions to ensure the correct configuration is live across all points-of-presence.
Audits backend origin mappings and extracts FQDN apex domains attached to services without having to manually navigate through the console settings.
Uses the MCP to deploy instant patches by promoting drafted versions, moving from a development state directly into production traffic.
Benefits of connecting Fastly MCP
Instantly deploy patches. Use the activate_service_version tool to promote a draft configuration, moving changes from test environments straight into production traffic.
Never worry about stale content again. A single prompt using purge_all_cache issues an absolute HTTP PURGE across all global points of presence for immediate data freshness.
Audit your network easily. You can run list_version_domains to verify every FQDN apex domain terminating at the edge, or use list_services to get a full inventory count.
Verify your infrastructure depth. Use list_version_backends to pinpoint the physical upstream origins (AWS/GCP) mapped inside any service version, ensuring no load balancer is missed.
Manage entire services lifecycle. You can list all running assets with list_services, get performance metrics via get_service_stats, and even clean up old infrastructure using delete_service.
Fastly MCP use cases
Rolling out an emergency security patch.
A Security Engineer needs to deploy a zero-day fix. Instead of manually logging into the console and promoting drafts, they simply ask their agent: 'Activate version 12 for service X.' The MCP executes activate_service_version instantly, making the changes live globally.
Troubleshooting a broken website image.
A Frontend Developer notices an old logo is showing up. They instruct their agent to 'Purge cache for service Y.' The MCP runs purge_all_cache, clearing the global CDN and forcing the network to grab the fresh version from the origin.
Verifying complex routing rules.
A Cloud Architect needs to know which domains are attached to a staging environment. They prompt their agent to run list_version_domains against the specific service version, getting an immediate list of all FQDNs terminating there.
Checking backend dependencies before deletion.
An SRE needs to decommission a service but must first confirm its connection points. They use list_version_backends on the target service version, verifying every mapped origin (AWS/GCP) is accounted for before running delete_service.
Fastly MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Confusing cache purging with deployment.
Manually purges the cache and then tries to deploy a fix, assuming the purge solved the issue. This wastes time because the actual code change needs explicit activation.
If content is stale, first run purge_all_cache. If the underlying configuration or patch is wrong, you must use activate_service_version before purging.
Assuming all services are active.
Attempting to manage a service using generic commands without first checking its status. This can lead to errors when trying to list versions or origins.
Always start by running list_services to confirm the exact name and existence of the target service before attempting any other operation.
Deleting a service without auditing backends.
Running delete_service on a crucial asset because its function is unknown. This might take down an entire backend origin (AWS/GCP) that another service relies upon.
Before deleting, use list_version_backends and get_service to fully map out all dependencies attached to the service.
When to use Fastly MCP
Use this MCP if your job requires constantly managing complex edge deployments. Specifically, if you need to deploy instant patches by promoting drafts (activate_service_version), or if cache invalidation is a core part of your workflow (purge_all_cache). You also need the ability to audit physical network details like domain names (list_version_domains) and backend origins (list_version_backends).
Don't use this MCP if you only need basic content storage or simple DNS record management. If your toolset is limited to just reading general usage metrics, get_service_stats handles that fine, but it won't help you deploy code or audit origins. This MCP is for hands-on infrastructure control; it’s not a read-only reporting tool.
Frequently asked questions about Fastly MCP
How do I purge the cache using Fastly MCP? +
You use the purge_all_cache tool by specifying the service ID. This sends a global HTTP PURGE command, invalidating all static content immediately.
Can I see what domains are attached to my services with Fastly MCP? +
Yes, you can use list_version_domains to get an exact list of FQDN apex domains tied to a specific service version for auditing.
What is the difference between creating and activating a service version with Fastly MCP? +
Creating (create_service) builds a new, draft configuration. Activating (activate_service_version) promotes that existing, tested draft to live traffic status.
Does Fastly MCP help me find my backend origins? +
Absolutely. Use list_version_backends to list all physical upstream Origins (AWS/GCP) associated with a given service version, helping you verify connectivity points.
What if I need to delete a Fastly service? Which tool should I use? +
Use the delete_service tool. However, always run list_version_backends first to ensure no other services rely on that infrastructure.