What was our cache hit ratio on www last week?
Fastly connects Memtro to your edge delivery. It lists your services with active version, the domains each serves and the origin backends it fetches from. It reports traffic per day, hour or minute in UTC: requests, cache hits and misses, hit ratio, bandwidth, origin fetches, errors and status codes. When asked, and once an administrator has granted the action by name, it can purge a URL, a surrogate key or a whole service from the cache, which cannot be undone and can load your origin, clone and lock versions, and activate a version, making it live worldwide within seconds.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Fastly tool, reads what it needs, and answers with the source cited.
These tools change something in Fastly. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Fastly is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which Fastly services do we run, and which version is active?
Which domains does the www service serve?
What was our cache hit ratio on www last week?
How many 5xx errors did the API service return yesterday, hour by hour?
Purge https://www.acme.com/pricing from the cache
Dan Fletcher, infrastructure engineer at Acme Ltd, asked why origin load rose last week. Memtro read the daily stats for the www service and showed the hit ratio falling on Wednesday, with origin fetches up the same day. It named the origin backends on the active version, so Dan knew where to look.
Sarah Chen, head of engineering at Northwind, asked Memtro to clear the old pricing page from the cache after a price change. Memtro purged that one URL on the www service in production, and the next request fetched the new page from origin.
The teams that lean on Fastly most, a question each of them asks, and what they connect beside it.
A record in Fastly is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn Fastly, open Account → API tokens and create a personal or automation token. Its user needs at least the Engineer role.
Set the scope to Read-only access (global:read), adding purge_select to purge by URL or surrogate key, purge_all to purge everything, or global only if version activation is wanted. Optionally limit it to chosen services, and copy it.
In Memtro, open Connections → Fastly and paste it into API token.
Ask: what was our cache hit ratio on www last week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Fastly tools are the same everywhere.
Only when you ask, and only what it has been granted: purge one URL from the CDN cache (hard, or soft to mark it stale); purge everything tagged with one surrogate key on a service; purge up to 256 named surrogate keys on a service; purge everything cached on a service (all traffic goes to origin until the cache refills); clone a service version into a new editable draft; activate a service version (changes live traffic handling); deactivate a service version; lock a service version against edits (permanent for that version); set the comment on a service version. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API token. In Fastly, open Account → API tokens and create a personal or automation token. Its user needs at least the Engineer role.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
