Fleet by Fractals Labs

Your fleet has a native MCP server. Point Claude, Cursor, or any MCP-capable agent at one URL and it can read your devices, earnings, hosts and payout queue, and even register new devices, all scoped to your organization. No exports, no copy-pasting dashboards into chat.

https://fleet.fractals.finance/api/mcp/mcp

Transport is Streamable HTTP. Every request needs one header: Authorization: Bearer <your API key>.

Connect in 30 seconds

Claude Code

claude mcp add --transport http fleet \
  https://fleet.fractals.finance/api/mcp/mcp \
  --header "Authorization: Bearer ffm_your_key_here"

Cursor, Claude Desktop, or anything that reads an MCP config

{
  "mcpServers": {
    "fleet": {
      "url": "https://fleet.fractals.finance/api/mcp/mcp",
      "headers": {
        "Authorization": "Bearer ffm_your_key_here"
      }
    }
  }
}

That is the entire setup. Ask your agent "list my devices" to confirm it works.

What your agent can do

Tool	What it does	Writes?
`list_devices`	Every device in your org, with an active-only filter	No
`get_device`	One device by serial number or id	No
`fleet_earnings`	Total token earnings over a month range (YYYY-MM)	No
`list_payout_requests`	Your payout queue, filterable by status	No
`list_hosts`	All hosts with saved wallets and device counts	No
`get_host`	One host with wallet, status, and assigned serials	No
`add_device`	Register a new device by serial, optional name	Yes
`create_external_host`	Add an off-platform host to your address book	Yes

The two write tools mirror dashboard actions. Neither moves money: approving and settling payouts stays in the dashboard, on purpose.

Get an API key

Keys look like ffm_ plus 32 characters and belong to your account, so agents see exactly what you see.

Open Settings in the dashboard.
Click New key, name it after whatever will use it (say "Claude Desktop"), and choose when it expires — 30 days, 90 days, a year, or never.
Copy the key. We show it once, so store it like a password. Paste it into the Authorization: Bearer header above.

The same page lists every key with its status, when it was last used, and when it expires, and lets you revoke any of them. A revoked or expired key stops working immediately.

Guardrails

Every tool is scoped to the organization behind the key. There is no cross-fleet access.
No tool can approve, settle, or send a payout. Money stays human-only.
Keys are stored as hashes, shown once, revocable, and stamped with last-used time.

Prompts to try

"Which of my devices earned the most from January through March?"
"List pending payout requests and tell me which hosts they belong to."
"Register device 78421C1BF529 and name it Rooftop unit."
"Do any of my hosts still have no wallet on file?"

Troubleshooting