Traffic, DNS, what the WAF blocked and which Workers run, asked in plain words.
Connect Cloudflare with an API token and Memtro lists your zones, reads DNS records, reports daily traffic and cache ratio, shows the busiest paths, says what the WAF blocked, and lists Workers scripts. The hourly sync writes each zone's finished day into memory. When you ask, and once an administrator has granted each action by name, it can create, change or delete DNS records, purge the cache, block or allow an IP or country, pause a zone and delete a Worker. DNS changes and blocks are live for real visitors, and a deleted Worker is gone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Cloudflare tool, reads what it needs, and answers with the source cited.
These tools change something in Cloudflare. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Cloudflare, choosing the same kinds; the tab shows Cloudflare's own steps. Each event can start a job, with the event as its input. Cloudflare sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Cloudflare 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.
How many unique visitors did example.com get each day last week, and what was the cache ratio?
Which paths had the most 5xx responses in the last 24 hours?
What did the WAF block on shop.example.com yesterday, and from which countries?
Is mail.example.com proxied, and what does its MX record point at?
Purge the cache for https://example.com/pricing
Support reports slow checkouts at 09:30. Someone asks Memtro which paths returned 5xx on the site in the last hour, and it answers from Cloudflare's request data with the paths, counts and share, and the top status codes, before anyone opens the dashboard.
Grace Lin is moving the marketing site and asks Memtro to point www.example.com at the new host. Memtro reads the current CNAME, changes its content in the zone and shows the record before and after. Visitors reach the new site as resolvers pick up the change.
The teams that lean on Cloudflare most, a question each of them asks, and what they connect beside it.
A record in Cloudflare 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 the Cloudflare dashboard open My Profile → API Tokens → Create Token → Create Custom Token (an account-owned token under Manage Account → API Tokens works the same way)
For reading give it Zone → Zone → Read, Zone → DNS → Read, Zone → Analytics → Read, Account → Account Settings → Read and Account → Workers Scripts → Read. For the actions add only the Edit permissions you want used, such as Zone → DNS → Edit or Zone → Cache Purge → Purge
Copy the token when it is created (it is shown once), then in Memtro open Connections → Cloudflare, paste the API token, add the Account id only if the token can see more than one account, and connect
Ask what the WAF blocked on your main domain in the last 24 hours
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Cloudflare tools are the same everywhere.
Only when you ask, and only what it has been granted: create, change or delete a DNS record (a live DNS change); purge cached content by URL, tag, host or prefix, or everything in a zone; block, challenge or allow an IP, range, ASN or country on a zone, or remove such a rule; pause Cloudflare on a zone, or resume it; delete a Workers script (permanent); re-check a pending zone's nameservers. 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. An hourly sync anchors recently changed Cloudflare records into memory as entities.
API token. In the Cloudflare dashboard open My Profile → API Tokens → Create Token → Create Custom Token (an account-owned token under Manage Account → API Tokens works the same way).
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Cloudflare, choosing the same kinds; the tab shows Cloudflare's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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
