Introduction
A macOS menu bar app for Cloudflare.
MFlare lets you know the moment a quota is filling up or a build finishes. It sits in your menu bar, keeps an eye on your Cloudflare accounts, and tells you what you’d otherwise have to open the dashboard to find out.
At a glance
Click the MFlare icon in the menu bar to open it. There are two tabs:
- Usage: how much of each quota you’ve used in the current billing period, and when it resets.
- Deployments: your Workers, each with its latest build or deployment.
If you watch more than one account, switch between them from the account menu at the top. The same menu shows the account’s Workers plan.
Usage and quotas
MFlare reads usage for five services and shows each one as used / quota:
| Service | Usage |
|---|---|
| Workers | Requests, CPU time (Workers Paid), build minutes, observability events (Workers Free) |
| Durable Objects | Requests, duration, rows read, rows written, storage |
| KV | Reads, writes, deletes, lists, storage |
| R2 | Class A operations, Class B operations, storage |
| D1 | Rows read, rows written, storage |
- Billing periods: some quotas reset every day and others every month, at 00:00 UTC. MFlare shows when each one resets, in your time zone. Storage is the size kept right now, so it doesn’t reset.
- Workers plan: Cloudflare doesn’t say which Workers plan an account is on, so you set it in Settings › Users (the account menu shows the current one and opens it). Until you do, quotas assume Workers Free. If Workers Paid ends on a known date, set that too, and MFlare switches back to Free quotas from then on.
- Free vs. Paid: on Workers Free a quota is a hard limit, and MFlare shows Limit reached when you hit it. On Workers Paid it’s an included allowance, and MFlare estimates what you’d be charged for usage beyond it.
- Usage alerts: MFlare sends a notification the first time a usage reaches 80% of its quota, and again at 100%, once each per billing period.
- Display: in Settings › Display, drag services to reorder them, or turn off a service or a single usage you don’t care about. Anything turned off isn’t shown, doesn’t alert, and isn’t fetched.
Usage refreshes about every 5 minutes. Click refresh in the popover to update it right away.
Builds and deployments
MFlare watches every Worker in every account it monitors, not just the account you’re looking at, for new builds and deployments.
- Builds: if a Worker is connected to a Git repository, Workers Builds runs a build after every
git push. MFlare notifies you when it starts, and when it succeeds or fails. - Deployments: a deployment from
wrangler deploy, the dashboard or the API gets a notification too, along with where it came from. - Build Log: right-click a build on the Deployments tab and choose View Build Log. A running build’s log keeps streaming in as it grows, and Copy All copies every line. The same menu can open the Worker in Cloudflare or copy the commit hash.
- Mute: right-click a Worker to mute it. To mute a whole account, turn it off under Settings › Notifications. A muted Worker or account still shows its data; it just doesn’t notify.
MFlare only notifies you about changes that happen while it’s running. When you sign in to a new account or MFlare comes back after being off, it takes what’s there as the starting point and doesn’t send notifications for what you missed.
The menu bar dot
When something is worth a look, a dot appears on the menu bar icon:
| Dot | Meaning |
|---|---|
| Red | A build or deployment failed and you haven’t seen it yet |
| Orange | A usage is near or past its quota, or a user needs to sign in again |
| Blue | A build is running |
| Green | A build or deployment finished since you last opened the Deployments tab |
Turning off Send notifications keeps the dot. An account turned off under Settings › Notifications doesn’t light the red, orange or green dot.
Users and accounts
Sign in with your Cloudflare login in your browser; MFlare never asks for your password or an API token. A user can access several accounts, and on Pro you can sign in more than one user, each with all of its accounts.
If Cloudflare stops accepting a user’s sign-in, MFlare shows it in orange and asks you to sign in again in Settings › Users.
Ask your AI
On Pro, MFlare runs a local MCP server, so agents such as Claude Code, Codex and Cursor can read your usage, quotas and build logs directly. See Connect an agent.
Free and Pro
| Free | Pro | |
|---|---|---|
| Usage, quotas and usage alerts | ✓ | ✓ |
| Build and deploy notifications, Build Log | ✓ | ✓ |
| Users and accounts | 1 user, 1 account | Unlimited |
| MCP server for AI agents | ✓ |
On Free, MFlare monitors one account. Other accounts of the same user are listed but not monitored. Pro is a one-time purchase that activates on 1 Mac; manage it in Settings › License.
Privacy
Your data stays on your Mac, and your sign-in is kept in the Keychain. MFlare doesn’t run a server of its own; the app talks to Cloudflare directly.
Requirements
macOS 14 or later, on Apple silicon or Intel.