We just dropped a new open-source Fastly (Model Context Protocol) MCP Server we think you’ll love. It lets you talk to your Fastly services using your AI coding assistant.
It lets you talk to your Fastly services using your favorite AI assistant. Want to check your cache hit ratio or find a specific domain? Just ask in plain English. No more hunting for that one specific CLI command. It’s all about making life easier by managing your configs, checking stats, and troubleshooting through a simple conversation.
We built it to scratch our own itch, and we’re opening it up because we believe it can help the community, too. We’re launching it early and intentionally with oss-tier-1 support because we want to build it with you. This is your invitation to peek behind the curtain, play with new toys, and help define the future of AI tooling at Fastly.
We built this for you and are super excited to see what you all come up with. We’ve got a bunch of example prompts in the README to get your ideas flowing.
So, what have you built? Found any cool or unexpected uses for it? Drop your best prompts and workflows below. We’d love to see them!
I have been playing around with the MCP, but when specifically asking stats related questions, which for me are the most important use cases, it tends to break.
For example, when I ask for bandwidth stats per region for a certain service, it ends up with this message:
I apologize for the difficulties with the Fastly CLI. It appears there’s a technical issue with the stats historical command where it’s automatically adding an invalid --json flag that’s causing errors. Based on my investigation, I can confirm that: Service Found: Service (Service ID: ID ) is active and running Available Regions: The following regions are available for traffic analysis: USA Europe Asia Asia_India Asia_SouthKorea ANZAC (Australia/New Zealand) LATAM Mexico SouthAmerica_std Africa_std Unfortunately, due to the CLI error, I cannot retrieve the actual traffic statistics for July 2025 per region at this moment. The issue appears to be with the Fastly CLI tool’s handling of the stats command.
Throughout the process, the issue with the invalid flag was mentioned multiple times:
It seems there’s an issue with the command format. Let me try without the extra --json flag that’s being added:
There seems to be an issue with the system automatically adding --json flag. Let me try the realtime stats instead to see if we can get recent data:
Thanks! A new release is out v0.1.8. The system prompt and help message have been changed to avoid references to --json and let the agent explore what works for each command. I hope that will solve the issue
https://github.com/fastly/mcp