Fleets

io.github.runFleets

Multi-site analytics as tools: GA4, Search Console, Cloudflare edge, PageSpeed, insights.

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.runfleets-cli": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "FLEETS_TOKEN": "<secret>"11      }12    }13  }14}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

FLEETS_TOKEN — Fleets personal access token (fl_...). Optional if you have already run `fleets login`; otherwise mint one at https://fleets.run/app/account?tab=cli.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1FLEETS_TOKEN=<secret> claude mcp add io.github.runfleets-cli -- npx -y fleets-mcp@0.2.2

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.runfleets-cli": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "FLEETS_TOKEN": "<secret>"11      }12    }13  }14}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.2.2
API key: FLEETS_TOKEN
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Fleets?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Fleets need an API key?

The publisher lists these environment variables: FLEETS_TOKEN.

What transport does Fleets use?

Fleets runs locally over stdio.

When was Fleets last checked?

Last checked 2026-10-28. Multi-site analytics as tools: GA4, Search Console, Cloudflare edge, PageSpeed, insights.

From the publisher

Documentation

fleets

Terminal CLI for Fleets. Per-site commands mirror the app UI tabs at https://fleets.run/app/<slug>/<tab>.

Install

npm install -g fleets

Authenticate

fleets login

Picks between two methods:

browser (default) — device flow: CLI prints a URL + 8-character code, auto-opens your browser, you click authorize, CLI finishes automatically.
paste a token — mint one in app → account → cli, paste it in.

Skip the prompt with a flag:

fleets login --browser     # force device flow
fleets login --paste       # force token paste

fleets login --token fl_xxxxxxxxxxxxxxxx   # paste in one shot (CI)
export FLEETS_TOKEN=fl_xxxxxxxxxxxxxxxx     # skip login entirely

Slug-first dispatch

The most intuitive way to run commands is to put the site slug first, like you're "inside" that site:

fleets fightbets                         # GA4 summary (defaults to stats)
fleets fightbets sources                 # top traffic sources
fleets fightbets funnel session_start view   # conversion funnel
fleets fightbets seo --range 30d         # GSC summary, last 30 days
fleets fightbets open settings           # print app URL

The legacy form fleets <command> <slug> (e.g. fleets sources fightbets) still works.

Commands

Setup

Command	Description
`fleets login`	Browser device-flow auth (no paste)
`fleets add <domain> [--detect]`	Create a site; `--detect` auto-links GA4 + GSC
`fleets connect <slug>`	Auto-detect GA4 + GSC via service account
`fleets connect <slug> --property <id>`	Set GA4 property explicitly
`fleets connect <slug> --gsc <site-url>`	Set GSC site explicitly

Analytics (per-site)

All accept --range (default 7d) and --json. Commands with top-N tables also accept --limit.

Command	Tab	Data source
`fleets list`	—	All your sites with sparkline + Δ7d
`fleets <slug>` / `fleets stats <slug>`	day	GA4 summary
`fleets <slug> sources`	sources	GA4 traffic sources
`fleets <slug> campaigns`	campaigns	GA4 UTM campaigns
`fleets <slug> referrals`	referrals	GA4 referrals
`fleets <slug> landers`	landers	GA4 landing pages
`fleets <slug> events`	events	GA4 events
`fleets <slug> users`	users	GA4 country + device breakdown
`fleets <slug> funnel <step1> <step2>…`	funnel	GA4 funnel
`fleets <slug> seo`	seo	Google Search Console
`fleets <slug> edge`	edge	Cloudflare Analytics
`fleets <slug> speed`	speed	PageSpeed Insights

Utility

Command	Description
`fleets <slug> export`	Daily GA4 CSV/JSON export
`fleets <slug> query "<text>"`	Natural-language analytics query
`fleets <slug> open [tab]`	Print the app URL for a site

MCP server

The same package ships an MCP server, fleets-mcp, so agents (Claude Code, Claude Desktop, Cursor, …) can pull your live Fleets analytics as tools. It reuses the CLI's auth — run fleets login once (or set FLEETS_TOKEN) and the MCP server picks up the same token from ~/.fleets/config.json.

Add it to a client

Claude Code:

claude mcp add fleets -- fleets-mcp

Claude Desktop / Cursor (claude_desktop_config.json or .cursor/mcp.json):

{
  "mcpServers": {
    "fleets": {
      "command": "fleets-mcp"
    }
  }
}

No global install? Use npx with the fleets-mcp launcher package:

{
  "mcpServers": {
    "fleets": {
      "command": "npx",
      "args": ["-y", "fleets-mcp"]
    }
  }
}

If you authenticate via env instead of fleets login, add "env": { "FLEETS_TOKEN": "fl_xxx" } to the server entry.

Tools

All read-only except log_change (writes a change-log entry). Every analytics tool takes a slug (from list_sites) and an optional range (7d, 30d, 24h).

Tool	What it returns
`list_sites`	All sites + connected sources (GA4 / Cloudflare / GSC) — start here
`stats`	GA4 summary: sessions, users, pageviews, events, engagement, bounce
`sources` · `campaigns` · `referrals` · `landers` · `events`	GA4 breakdowns (accept `limit`)
`users` · `devices` · `demographics`	GA4 audience breakdowns
`funnel`	GA4 conversion funnel across `steps` (2+)
`seo`	Google Search Console summary
`edge`	Cloudflare edge analytics (bots, humans, cache)
`speed`	PageSpeed Insights + Core Web Vitals
`insights`	AI-ready signals worth investigating (optionally per `site`)
`ask`	Natural-language question answered server-side with citations
`log_change` · `recall`	Write / read the per-site change log

Environment variables

Variable	Description
`FLEETS_TOKEN`	Personal access token. Skip `fleets login` entirely — useful for CI. Overrides `~/.fleets/config.json`.

Range format

All --range flags accept:

7d — last 7 days
30d — last 30 days
90d — last 90 days
24h — last 24 hours (rounds to 1 day)

Requirements

Node.js >= 22 (LTS)
Works on macOS, Linux, Windows

Fleets

io.github.runFleets

Multi-site analytics as tools: GA4, Search Console, Cloudflare edge, PageSpeed, insights.

Cloud Infrastructure

Add to Cursor Add to VS Code Run on PlugMCP

GitHub npm Website

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.runfleets-cli": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "FLEETS_TOKEN": "<secret>"11      }12    }13  }14}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

FLEETS_TOKEN — Fleets personal access token (fl_...). Optional if you have already run `fleets login`; otherwise mint one at https://fleets.run/app/account?tab=cli.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1FLEETS_TOKEN=<secret> claude mcp add io.github.runfleets-cli -- npx -y fleets-mcp@0.2.2

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.runfleets-cli": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "FLEETS_TOKEN": "<secret>"11      }12    }13  }14}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.2.2
API key: FLEETS_TOKEN
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Fleets?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Fleets need an API key?

The publisher lists these environment variables: FLEETS_TOKEN.

What transport does Fleets use?

Fleets runs locally over stdio.

When was Fleets last checked?

Last checked 2026-10-28. Multi-site analytics as tools: GA4, Search Console, Cloudflare edge, PageSpeed, insights.

From the publisher

Documentation

fleets

Terminal CLI for Fleets. Per-site commands mirror the app UI tabs at https://fleets.run/app/<slug>/<tab>.

Install

npm install -g fleets

Authenticate

fleets login

Picks between two methods:

browser (default) — device flow: CLI prints a URL + 8-character code, auto-opens your browser, you click authorize, CLI finishes automatically.
paste a token — mint one in app → account → cli, paste it in.

Skip the prompt with a flag:

fleets login --browser     # force device flow
fleets login --paste       # force token paste

fleets login --token fl_xxxxxxxxxxxxxxxx   # paste in one shot (CI)
export FLEETS_TOKEN=fl_xxxxxxxxxxxxxxxx     # skip login entirely

Slug-first dispatch

The most intuitive way to run commands is to put the site slug first, like you're "inside" that site:

fleets fightbets                         # GA4 summary (defaults to stats)
fleets fightbets sources                 # top traffic sources
fleets fightbets funnel session_start view   # conversion funnel
fleets fightbets seo --range 30d         # GSC summary, last 30 days
fleets fightbets open settings           # print app URL

The legacy form fleets <command> <slug> (e.g. fleets sources fightbets) still works.

Commands

Setup

Command	Description
`fleets login`	Browser device-flow auth (no paste)
`fleets add <domain> [--detect]`	Create a site; `--detect` auto-links GA4 + GSC
`fleets connect <slug>`	Auto-detect GA4 + GSC via service account
`fleets connect <slug> --property <id>`	Set GA4 property explicitly
`fleets connect <slug> --gsc <site-url>`	Set GSC site explicitly

Analytics (per-site)

All accept --range (default 7d) and --json. Commands with top-N tables also accept --limit.

Command	Tab	Data source
`fleets list`	—	All your sites with sparkline + Δ7d
`fleets <slug>` / `fleets stats <slug>`	day	GA4 summary
`fleets <slug> sources`	sources	GA4 traffic sources
`fleets <slug> campaigns`	campaigns	GA4 UTM campaigns
`fleets <slug> referrals`	referrals	GA4 referrals
`fleets <slug> landers`	landers	GA4 landing pages
`fleets <slug> events`	events	GA4 events
`fleets <slug> users`	users	GA4 country + device breakdown
`fleets <slug> funnel <step1> <step2>…`	funnel	GA4 funnel
`fleets <slug> seo`	seo	Google Search Console
`fleets <slug> edge`	edge	Cloudflare Analytics
`fleets <slug> speed`	speed	PageSpeed Insights

Utility

Command	Description
`fleets <slug> export`	Daily GA4 CSV/JSON export
`fleets <slug> query "<text>"`	Natural-language analytics query
`fleets <slug> open [tab]`	Print the app URL for a site

MCP server

Add it to a client

Claude Code:

claude mcp add fleets -- fleets-mcp

Claude Desktop / Cursor (claude_desktop_config.json or .cursor/mcp.json):

{
  "mcpServers": {
    "fleets": {
      "command": "fleets-mcp"
    }
  }
}

No global install? Use npx with the fleets-mcp launcher package:

{
  "mcpServers": {
    "fleets": {
      "command": "npx",
      "args": ["-y", "fleets-mcp"]
    }
  }
}

If you authenticate via env instead of fleets login, add "env": { "FLEETS_TOKEN": "fl_xxx" } to the server entry.

Tools

All read-only except log_change (writes a change-log entry). Every analytics tool takes a slug (from list_sites) and an optional range (7d, 30d, 24h).

Tool	What it returns
`list_sites`	All sites + connected sources (GA4 / Cloudflare / GSC) — start here
`stats`	GA4 summary: sessions, users, pageviews, events, engagement, bounce
`sources` · `campaigns` · `referrals` · `landers` · `events`	GA4 breakdowns (accept `limit`)
`users` · `devices` · `demographics`	GA4 audience breakdowns
`funnel`	GA4 conversion funnel across `steps` (2+)
`seo`	Google Search Console summary
`edge`	Cloudflare edge analytics (bots, humans, cache)
`speed`	PageSpeed Insights + Core Web Vitals
`insights`	AI-ready signals worth investigating (optionally per `site`)
`ask`	Natural-language question answered server-side with citations
`log_change` · `recall`	Write / read the per-site change log

Environment variables

Variable	Description
`FLEETS_TOKEN`	Personal access token. Skip `fleets login` entirely — useful for CI. Overrides `~/.fleets/config.json`.

Range format

All --range flags accept:

7d — last 7 days
30d — last 30 days
90d — last 90 days
24h — last 24 hours (rounds to 1 day)

Requirements

Node.js >= 22 (LTS)
Works on macOS, Linux, Windows