fastly-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fastly_get_configA | Read-only: retrieve one tenant/user or tenant/account configuration key from Postgres. Never stores secrets. |
| fastly_set_configA | Mutating: persist non-secret tenant/user or tenant/account configuration in Postgres. Reject tokens and secrets; requires the admin key when configured. |
| service_query_suggestionC | Discover MCP tool schemas and get query/tool recommendations for a workflow intent. |
| service_connection_infoB | Return MCP server and target service connection details. |
| service_scope_infoC | Return app/tenant/principal scoping metadata used by Postgres config and Vault token index paths. |
| service_list_endpointsB | List documented/implemented target service HTTP endpoints exposed by this MCP server. |
| service_health_checkA | Read-only: validate a user-scoped Fastly token with GET /tokens/self. Requires a Fastly token. |
| fastly_list_servicesA | Read-only: list services visible to the supplied Fastly user token. Follow with fastly_list_versions or service_api_request. |
| fastly_list_versionsA | Read-only: list versions for a Fastly service. Requires serviceId and a user token. |
| fastly_purge_serviceA | High-risk mutation: purge all cached content for a Fastly service. Confirm serviceId and require MCP_ADMIN_AUTH_KEY when configured. |
| fastly_update_user_tokenA | High-risk mutation: persist or rotate one tenant/user or tenant/account Fastly token in Vault. Never use for configuration; provide scope and admin authorization. |
| service_api_requestD | Generic target service HTTP API call. Supports all available endpoints while enforcing host/auth safeguards. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose. Config get/set, service introspection, and Fastly-specific operations (list services, versions, purge, token update) are all unambiguously separated. Even similar-sounding tools like fastly_get_config and service_scope_info have distinct descriptions (config retrieval vs. scoping metadata).
Names follow a verb_noun pattern within two clear prefix groups: 'fastly_' for Fastly-specific actions (fastly_list_services, fastly_purge_service) and 'service_' for service-level introspection (service_list_endpoints, service_health_check). While not a single uniform prefix, the grouping is logical and internally consistent, so the pattern is predictable after seeing a few examples.
12 tools is well-scoped for a Fastly management MCP. The set covers config, token management, service listing, version listing, purge, health checks, and generic API access without being bloated. Each tool serves a clear purpose, and the count is appropriate for the domain.
The tool surface covers core workflows: config get/set, token rotation, service listing, version listing, purge, health checks, and endpoint discovery. While it lacks explicit create/delete service operations, the generic service_api_request fills that gap by allowing arbitrary API calls. Minor gaps exist (e.g., no dedicated service version creation), but agents can work around them via the generic endpoint.