# Fastly MCP for AI Agents AI Agent Connect

> Fastly MCP lets you manage your edge computing and CDN settings through your AI agent. You can activate new service versions, manage domains and backends, and purge cache globally without leaving your chat or IDE. It connects your Fastly account to your AI client so you can handle production deployments and traffic auditing using natural language commands.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_DoQHJFChafBsNpZF2vkvStONLhFdmK4tw0VbuS3U/ai-agent-connect
- **Tags:** cdn, edge-computing, waf, cache-purging, web-security, network-optimization

## Description

Managing an edge network usually involves a lot of tab hopping. You have to log in, find the right service, navigate to the versions tab, find the right ID, and then click promote. If you're doing this during a high pressure incident, every second counts and the risk of a manual error is high. This Connector changes that by letting you talk to your Fastly account directly through your AI agent. Instead of manually navigating the dashboard to find a specific service or checking if a version is live, you just ask your agent to do it for you. You can move drafted configurations into production, check where your traffic is actually landing, and clear out stale cache across the entire global network with a single request. Since Vinkius hosts this Connector, you can keep your entire infrastructure management in one place while keeping your workflow focused on the actual work. It's about getting rid of the dashboard fatigue and making edge configuration as fluid as a conversation. You can audit your domains, check your backend origins, and pull usage stats without ever having to hunt for a specific URL in your browser. It turns complex infrastructure tasks into simple commands. This means you can handle the heavy lifting of CDN maintenance while staying in your primary workspace. It bridges the gap between high level intent and low level configuration changes.

## Tools

### create_service
Creates a new Fastly service. Use this to set up new environments quickly.

### delete_service
Removes a specific Fastly service. This helps keep your account clean.

### get_me
Checks your current API token identity. Use this to verify your connection is active.

### get_service
Retrieves all details for a specific service. It's great for quick audits.

### list_version_backends
Lists all backend origins for a specific service version. Use this to verify upstream connections.

### list_version_domains
Lists all domains for a specific service version. This helps you audit your edge routing.

### list_services
Lists all services in your account. It's the quickest way to see your full fleet.

### list_service_versions
Lists all configuration versions for a service. Use this to see your deployment history.

### activate_service_version
Promotes a specific configuration version to live status. This is the fastest way to push a hotfix.

### get_service_stats
Pulls usage statistics for a service. Use this to monitor traffic patterns.

### get_service_version
Shows details for a specific version. It helps you see what's currently active.

### purge_all_cache
Purges all cached content for a specific service. Use this to clear stale data globally.

## Prompt Examples

**Prompt:** 
```
Which versions do I have for the production service?
```

**Response:** 
```
I found 4 versions for 'Prod-Main-CDN':

| Version | Status |
| :--- | :--- |
| 12 | **Active** |
| 13 | Draft |
| 14 | Draft |
| 15 | Draft |

Version 15 is the most recent draft. Would you like to see the details for any of these?
```

**Prompt:** 
```
Clear the cache for the media service.
```

**Response:** 
```
Cache purge initiated. I've sent a global HTTP PURGE for the 'Media-Assets' service. All static content is now invalidated, and the network will fetch fresh data from your origins immediately.
```

**Prompt:** 
```
Show me the backends for version 15.
```

**Response:** 
```
Here are the backend origins for version 15:

*   **Origin A**: 192.168.1.1:80
*   **Origin B**: 192.168.1.2:80

Both origins are currently active and mapped to this configuration.
```

## Capabilities

### Promote new configurations to live status
Activate a specific configuration version for a service to push changes to production.

### Clear global cache for specific services
Issue a global purge for all cached content of a specific service instantly.

### Audit backend origin mappings
List all backend origins for a specific service version to verify upstream connections.

### Check live traffic version pointers
Identify which specific configuration version is currently controlling live traffic.

### List and manage FQDN domains
Extract and manage all apex domains terminated at the Fastly Edge.

### Get real-time service usage stats
Retrieve usage statistics for a specific service to monitor traffic patterns.

## Use Cases

### Emergency Cache Clear
A developer notices a stale asset on the live site and asks the agent to purge all cache for the production service.

### Hotfix Deployment
An SRE needs to push a security patch and tells the agent to activate version 22 for the main CDN service.

### Origin Audit
A cloud architect wants to verify that the staging environment is pointing to the correct AWS origin using list_version_backends.

### New Service Setup
A dev wants to spin up a new test environment and asks the agent to create a service with specific parameters.

## Benefits

- Push hotfixes faster by using activate_service_version to promote configurations without manual dashboard navigation.
- Clear stale content globally using purge_all_cache to ensure users see the latest data immediately.
- Audit your infrastructure by using list_version_backends to see exactly where your traffic is being routed.
- Monitor health easily with get_service_stats to keep an eye on your service usage and traffic.
- Simplify environment setup by using create_service and list_services to manage your entire fleet.

## How It Works

The bottom line is you get a direct command line for your edge cloud powered by natural language.

1. Subscribe to the Fastly MCP on Vinkius
2. Enter your Fastly API Token from your account settings
3. Ask your AI agent to list services, promote versions, or purge cache

## Frequently Asked Questions

**Can I use the Fastly MCP to clear my cache?**
Yes, it lets your agent issue a global purge for any service. This is great for clearing out stale content instantly without needing to navigate the dashboard.

**How do I activate a new version with Fastly MCP?**
You just tell your agent which version number or name to promote. It handles the activation for you, making it easy to push hotfixes to production.

**Does the Fastly MCP support multiple services?**
Yes, it can list and manage all services in your account. You can switch between different environments and services easily in chat.

**Can I audit my backend origins with Fastly MCP?**
You can use it to list all backends for a specific version. This helps you verify where your traffic is going and ensure your routing is correct.

**Is the Fastly MCP safe for production?**
Yes, it uses your existing API tokens. It performs the same actions you'd do in the dashboard but through a chat interface, keeping your security model intact.

**Can I see my service stats using Fastly MCP?**
You can ask your agent for usage statistics on any service. It'll pull the latest data for you so you can monitor traffic patterns on the fly.

**Can my agent purge the entire Fastly cache for a specific service?**
Yes. Use the 'purge_all_cache' tool with your Service ID. The agent will issue absolute HTTP PURGE instructions globally, vaporizing the complete surrogate cache for static endpoints immediately.

**How do I activate a drafted configuration version via chat?**
Use the 'activate_service_version' tool. Provide the Service ID and the version number. The agent will force the compilation of that VCL version and promote the draft to active, promoting your changes to production flawlessly.

**Can I check which backend origins are connected to a service version through the agent?**
Absolutely. Use the 'list_version_backends' tool. Your agent will read the exact upstream AWS/GCP endpoints mapped inside your active or drafted configuration, helping you verify origin and port constraints.