LABSCO SUMMARY

Broad reach into a live CDN, at 0.1.0 and marked beta.

Because it fronts Fastly's whole API, the same connection that reads your cache hit ratio can also purge cache and change service configuration. That is the point, but treat the key you hand it as production credentials — the README does not publish a per-tool list, so the safe read is that whatever your key can do, the assistant can ask for.

What it is

An MCP server that puts the Fastly API behind an AI assistant. Fastly's API covers everything the web UI does, so the reachable surface is broad: CDN service configuration, cache purges, WAF and TLS settings, real-time and historical stats, and VCL or Compute@Edge deployment. The assistant never sees your key — it talks to this local helper, which holds it.

What you get

Your services listed, and the domains configured on any one of them
Cache purged for a named service
Traffic patterns and cache hit ratio read back over a time window
Backend servers and other configuration read out of a service
The wider Fastly API surface — WAF rules, TLS, VCL and Compute@Edge — reachable through the same connection

Requirements

A Fastly account and an API key, passed as FASTLY_API_KEY in the client's env block. The Fastly CLI must be installed. The README's config runs it as node <YOUR_PATH_TO_FASTLY_MCP>, so you install from the repository rather than a published binary; the package is named fastly-mcp-server at 0.1.0 and the badges mark the project beta and Node.js 16+.

Setup effort

Build from source — get the source, then follow the project's own run instructions

See installation options

USE CASES

01

Getting oriented in an account you inherited

Ask for every service and the domains attached to each, instead of clicking through the Fastly UI service by service.

02

Clearing a stale asset after a deploy

Name the service and ask for a purge, then confirm the cache hit ratio recovers over the following minutes.

03

Explaining a traffic spike

Pull the traffic pattern for the last week and the backend configuration together, so the shape and the cause are in the same answer.

BEFORE YOU INSTALL

What to know first

Requires

node on PATH
FASTLY_API_KEY in your environment

INSTALLATION

Connect your client

You clone and build this one yourself.

Server setup

Configuration file

JSON

{
  "mcpServers": {
    "fastly": {
      "command": "node",
      "args": [
        "<YOUR_PATH_TO_FASTLY_MCP>"
      ],
      "env": {
        "FASTLY_API_KEY": "<YOUR_FASTLY_API_KEY>"
      }
    }
  }
}

node

TERMINAL

node <YOUR_PATH_TO_FASTLY_MCP>

FastlyMCP