Every Worker, and what it is doing.
See requests and errors for every Worker in your Cloudflare account, the latest deploy for each, and your D1 databases, with a Worker that starts failing flagged on Overview.
Connect Cloudflare in one click, read-only. It cannot deploy or change anything. A read-only API token works too.
What LopeBase reads
This connector reads your Cloudflare account as a whole: its Workers, their traffic over the last day, their latest deploys, and its D1 databases. Cloudflare Web Analytics for each site is a separate connector that can share the same sign-in.
- WorkersEvery Worker in the account by name, with requests, errors, and error rate over the last 24 hours, and when it was last changed. Busiest first.
- Latest deploysFor up to 25 Workers, when each one last shipped, where the deploy came from, who shipped it, and the deploy message if there was one.
- D1 databasesEach database's name, size in megabytes, number of tables, and when it was created, for up to 100 databases.
Request and error counts come from Cloudflare's GraphQL analytics API, read with the Account Analytics permission.
How to connect it
Two ways in. Both are read-only, and one connection covers the whole account.
- 01
In LopeBase, open Manage, then Connections, and pick Cloudflare under Infrastructure. Press Connect Cloudflare.
- 02
Approve read-only access on Cloudflare's screen. Analytics is required; Workers and D1 can be turned off there if you only want traffic. With the sign-in, LopeBase never sees your Workers' code.
- 03
Pick the account to watch, if you have more than one. Workers, deploys, and D1 fill in from there.
Prefer a token? The link in the connect guide opens Cloudflare's token page with the name and three read permissions filled in: Workers Scripts, D1, and Account Analytics. Press Continue to summary, then Create Token, and paste it with your account ID. See Connect your tools.
What LopeBase does with it
LopeBase only reads Workers, deploys, D1, and analytics. It never deploys or changes anything in Cloudflare.
- Worker error ratesA Worker with 5% of requests failing over 24 hours is worth a look, and 20% is flagged as broken. Workers with fewer than 100 requests are left out, so a quiet test Worker never cries wolf.
- Named in the warningNeeds attention names up to three failing Workers, worst first, with their failure rate and request count.
- AlertsA failing Worker counts under Builds and errors in your alert settings, by email or browser push.
- A broken connectionIf the sign-in or token stops working, the connection shows under Needs attention with a Reconnect link.
Questions it answers
If your products run on Workers, this is the infrastructure view next to the business view.
- Which Worker is failing?The error rate for every busy Worker, without opening each one in the dashboard.
- What shipped last, and who shipped it?The latest deploy per Worker, with its source and message, newest first.
- Is a D1 database growing fast?Size and table count for each database on one list.
- Is the site up, as well as the Worker healthy?Add uptime checks for each product's address, and a health address that tests D1 with your own credentials.
- Did a build break it?With GitHub, a failing Actions run on the main branch is flagged too.
- Can my agent see it?Over MCP, get_health includes a failing Worker among the checks it returns. See the MCP server.
What it does not do
- No deploys or rollbacksShip and roll back with Wrangler or the dashboard. LopeBase reads only.
- No logsIt reads request and error counts, not log lines or live tails.
- Workers and D1 onlyIt does not read KV, R2, Queues, or Durable Objects.
- Account wide, not per propertyWorkers are listed for the whole account by name, rather than split up by property.
Your AI agent can read Cloudflare Web Analytics over MCP too. See what it can ask.
Cloudflare questions
Something else? Contact us.
Can I deploy or roll back from LopeBase?
Not today. The Cloudflare connector reads. Deploy and roll back with Wrangler or the dashboard.
Do I connect it once per product?
No. One sign-in covers the whole Cloudflare account, and the same sign-in connects Web Analytics for each product.
Which permissions does a token need?
Read access to Workers scripts, D1, and account analytics. The link in the connect guide fills them in.
Can I connect only traffic, without Workers?
Yes. On Cloudflare's sign-in screen, turn off Workers and D1 and keep Analytics. Web Analytics still works for each site.
Why is a Worker with errors not flagged?
It needs at least 100 requests in 24 hours and a failure rate of 5% or more. Below that, a handful of errors swings the rate too much to mean anything.
How is the Cloudflare sign-in stored?
The connection keeps a sealed handle to the sign-in, never a raw token, and LopeBase asks Cloudflare for a fresh short-lived token when it reads. A pasted API token is stored encrypted instead. Revoke either one in Cloudflare at any time.
Put Cloudflare next to everything else.
Free for one property. No card.