Connect an agent

MFlare runs a local MCP server on your Mac. Once an agent is connected, it can ask how much of each quota is left, when it resets, and how a Worker’s latest builds and deployments went, instead of guessing the limits of your Cloudflare plan.

What is MCP?Copy Anchor Link

MCP (Model Context Protocol) is an open protocol that lets AI assistants call tools and read data from outside sources. MFlare’s MCP server hands an agent the same usage, quotas and build history you see in the menu bar, as structured data it can reason about.

Turn on the MCP serverCopy Anchor Link

1. Open MFlare’s Settings › MCP.
2. Turn on MCP Server. Its status changes to Running. The first time, MFlare creates a token.
3. The port is 47823 by default. If it’s taken, pick another from 1024 to 65535; turn the MCP server off first to change it.

Every client below needs the same two things:

• URL: http://127.0.0.1:47823/mcp (or your port, if you changed it)
• Header: Authorization: Bearer <token>, with the token from Copy next to Token

In the examples, replace <token> with your token, and 47823 with your port if you changed it.

ToolsCopy Anchor Link

Every tool is read-only and answers from what MFlare already has, so calling one doesn’t send extra requests to Cloudflare (except get_build_log). When account_id is left out, a tool reads the account MFlare currently shows.

A few things the server also tells the agent, so its answers stay accurate:

• On the Free Workers plan a quota is a hard limit. On Workers Paid it’s an included allowance, and usage beyond it is billed, so get_usage adds the overage price and an estimated cost.
• MFlare doesn’t read the Workers plan from Cloudflare; you set it in MFlare. If you haven’t, the agent is told the quotas assume Free.
• Billing periods reset at 00:00 UTC, and every time is in UTC. Usage is refreshed about every 5 minutes.
• get_build_log reads a long or still-running log in pages: the agent calls it again with the returned cursor to read on.

ConfigurationCopy Anchor Link

MFlare’s MCP server uses the Streamable HTTP transport and only listens on your Mac, so it works with clients that run on your Mac, not with cloud-hosted ones such as ChatGPT connectors.

Claude CodeCopy Anchor Link

Under Agents in Settings › MCP, click Claude Code and MFlare copies the command that connects it, with your port and token already filled in. Paste it into Terminal and run it once:

claude mcp add --scope user --transport http MFlare http://127.0.0.1:47823/mcp --header "Authorization: Bearer <token>"

--scope user makes MFlare available in every project. Run claude mcp list to check it’s connected.

CodexCopy Anchor Link

Under Agents, click Codex and run the copied command in Terminal. It removes any MFlare added before and writes the token into Codex’s config.toml, so running a fresh copy updates it.

To set it up by hand, add this to ~/.codex/config.toml:

[mcp_servers.MFlare]
url = "http://127.0.0.1:47823/mcp"

[mcp_servers.MFlare.http_headers]
Authorization = "Bearer <token>"

Claude DesktopCopy Anchor Link

Claude Desktop’s config file starts local servers only, so connect it through mcp-remote, which needs Node.js.

1. Open Claude Desktop and go to Settings › Developer.
2. Click Edit Config, and open claude_desktop_config.json.
3. Add MFlare:

{
  "mcpServers": {
    "MFlare": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://127.0.0.1:47823/mcp",
        "--header",
        "Authorization:${MFLARE_AUTH}"
      ],
      "env": {
        "MFLARE_AUTH": "Bearer <token>"
      }
    }
  }
}

4. Restart Claude Desktop.

The header goes through env because Claude Desktop doesn’t pass spaces inside args reliably.

CursorCopy Anchor Link

1. Open Cursor and go to Settings › Tools & MCP.
2. Click New MCP Server, which opens ~/.cursor/mcp.json, and add MFlare:

{
  "mcpServers": {
    "MFlare": {
      "url": "http://127.0.0.1:47823/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Visual Studio CodeCopy Anchor Link

You need the GitHub Copilot Chat extension.

1. Open the Command Palette (Cmd + Shift + P) and run MCP: Open User Configuration.
2. Add MFlare. VS Code asks for the token the first time it starts the server and keeps it in its secret storage:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "mflare-token",
      "description": "MFlare MCP token",
      "password": true
    }
  ],
  "servers": {
    "MFlare": {
      "type": "http",
      "url": "http://127.0.0.1:47823/mcp",
      "headers": {
        "Authorization": "Bearer ${input:mflare-token}"
      }
    }
  }
}

WindsurfCopy Anchor Link

1. Open Windsurf Settings › Cascade.
2. Click Manage MCPs, then View raw config.
3. Add MFlare:

{
  "mcpServers": {
    "MFlare": {
      "serverUrl": "http://127.0.0.1:47823/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Gemini CLICopy Anchor Link

Add MFlare to mcpServers in ~/.gemini/settings.json, then restart Gemini CLI:

{
  "mcpServers": {
    "MFlare": {
      "httpUrl": "http://127.0.0.1:47823/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

GitHub Copilot CLICopy Anchor Link

Add MFlare to ~/.copilot/mcp-config.json, or run /mcp add in Copilot CLI and fill in the same values:

{
  "mcpServers": {
    "MFlare": {
      "type": "http",
      "url": "http://127.0.0.1:47823/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      },
      "tools": ["*"]
    }
  }
}

Run /mcp show to check it’s available.

OpenCodeCopy Anchor Link

Add MFlare to ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "MFlare": {
      "type": "remote",
      "url": "http://127.0.0.1:47823/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      },
      "enabled": true
    }
  }
}

ZedCopy Anchor Link

Open Zed’s settings file (Cmd + ,) and add MFlare under context_servers:

{
  "context_servers": {
    "MFlare": {
      "url": "http://127.0.0.1:47823/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Usage examplesCopy Anchor Link

Once connected, try asking:

• “How’s my Cloudflare usage looking?”
• “Is anything close to its quota?”
• “How many KV writes do I have left today, and when does it reset?”
• “I’m about to bulk-write to KV. Do I have enough writes left today?”
• “What would I pay for this month’s overage on Workers Paid?”
• “Which of my Workers deployed most recently?”
• “Why did api-gateway’s last build fail?”
• “Show me only the errors from api-gateway’s latest build log.”

TroubleshootingCopy Anchor Link

• The agent can’t connect. Check that MCP Server is on and shows Running, and that the port in your config matches the one in MFlare. MFlare has to be running too.
• Requests are refused as unauthorized. The token was regenerated, or MFlare went back to Free and forgot it. Copy the token or the connect command again and update your config.
• The quotas look wrong. Check the Workers plan you set for the account in MFlare. MFlare doesn’t read it from Cloudflare, so an account with no plan set is treated as Free.

SecurityCopy Anchor Link

• The MCP server only listens on 127.0.0.1, so nothing outside your Mac can reach it. It also turns away requests from web pages that aren’t on this Mac.
• Every request needs the token. The connect commands and config files include it too, so keep them to yourself.
• If the token may have leaked, click Regenerate… next to Token. The old token stops working right away, and connected agents need the new token or a fresh copy of the command.
• Going back to Free turns the MCP server off and forgets its token. After reactivating Pro, turn it on again and copy the command again.