CLOUD OPERATIONS / Fastly
Fastly MCP Server
Fastly's official TypeScript MCP server giving agents access to the Fastly API: look up services, domains and TLS settings, check traffic and usage, manage dictionaries and ACLs, purge content and make configuration changes. Tier 1 open-source support, stdio and HTTP transports.
“The Fastly MCP server lets MCP clients work with the Fastly API.”
01 / THE REASONING
Why this made the selection.
- This is the publisher's own server for CDN service management and traffic analysis, with Tier 1 support declared against Fastly's published open-source support policy.
- Token guidance is scoped by design: the README instructs starting with a read-only API token and escalating to write scope only when changes are intended, keeping the token in the client environment rather than in prompts.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Fastly MCP repository at pinned revision 8059c142f87522196bdc34ef6fcf478496effb1b: README documents service and domain lookup, traffic and usage checks, dictionary and ACL management, purging and configuration changes, and per-client setup; package.json names @fastly/mcp 2.3.0 with bin fastly-mcp and a start:http script; LICENSE is MIT (Copyright 2026 Fastly Inc.).
- src/index.js at the pinned revision is a Node entrypoint importing runCli; REMOTE-HTTP.md documents running the server over HTTP for remote and shared deployments.
- Fastly API token guide linked from the README: create the narrowest token that fits the work, start read-only for investigation, and use write access only when changes are intended.
- README.md at the same commit: How it works, Running over HTTP, Large results, Secret encryption
- src/tools/ and src/sandbox.js at the same commit
- Repository tree at the same commit (file extensions)
Our findings
- The repository was rewritten from an earlier Go implementation; an unpinned raw fetch of the README served the stale Go-era text from CDN cache during this review, which is why every file was read at the pinned SHA.
- Tier 1 support in Fastly's open-source policy commits the publisher to maintaining the project, distinguishing it from reference implementations.
- The README describes three tools used together: search finds API methods, inspect returns a method’s documentation, and execute runs a short JavaScript snippet with the Fastly client set up with the API token. src/tools/ holds search.js, inspect.js and execute.js.
- src/sandbox.js runs each snippet in a child process inside a node:vm context and authenticates the Fastly client there with the token.
- HTTP mode (--transport http) listens on http://127.0.0.1:8231/mcp, loopback only and with no authentication by default. FASTLY_MCP_HTTP_AUTH_TOKEN adds a bearer token. --remote-http takes each caller’s own Fastly token.
- In local mode API output, including any credentials Fastly returns, reaches the client as returned unless secret encryption is enabled. Remote mode always encrypts recognised secrets.
- Correction, 2026-10-13: the repository tree at this commit contains no .ts file, and the 27 source files under src/ are .js. The record previously listed TypeScript as the language and said the rewrite was to TypeScript.
Not established by this review
- No Fastly API token was created and no service, purge or configuration call was executed.
- The execute tool, the HTTP and remote-HTTP modes and secret encryption were not run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
npx -p @fastly/mcp fastly-mcp Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Create a Fastly API token scoped to the work the assistant should do — read-only for investigation, write access only for changes.
- Add the mcpServers block to the client configuration with FASTLY_API_TOKEN in the environment.
- Ask the assistant to list your Fastly services to verify the connection.
Before you start
- A Fastly account with an API token.
- Node.js 24.12.0+ or Bun 1.0+ on the machine running the server.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"fastly": {
"command": "npx",
"args": [
"-p",
"@fastly/mcp",
"fastly-mcp"
],
"env": {
"FASTLY_API_TOKEN": "your-token-here"
}
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/fastly/mcp/blob/8059c142f87522196bdc34ef6fcf478496effb1b/README.md
Supports: summary, upstreamDescription, bestFor, limitations, install, configExample, compatibility, Tools search, inspect and execute, HTTP mode and bearer token, Result files, Secret encryption, transports
https://github.com/fastly/mcp/blob/8059c142f87522196bdc34ef6fcf478496effb1b/package.json
Supports: repository, revision, language, transports
https://github.com/fastly/mcp/blob/8059c142f87522196bdc34ef6fcf478496effb1b/LICENSE
Supports: license
- Fastly API token guide ↗Checked
https://docs.fastly.com/en/guides/using-api-tokens
Supports: access, whySelected
https://github.com/fastly/mcp/blob/8059c142f87522196bdc34ef6fcf478496effb1b/src/sandbox.js
Supports: execute runs in a child process with node:vm, Token authenticates the Fastly client
https://github.com/fastly/mcp/tree/8059c142f87522196bdc34ef6fcf478496effb1b/src/tools
Supports: search.js, inspect.js, execute.js, language