Fleets

What is Fleets?

Fleets is a multi-site analytics MCP server for AI agents. It provides read-only access to GA4, Search Console, Cloudflare edge, and PageSpeed data across every site you run, plus audits that return paste-ready fixes. It is meant for developers and AI agents that need aggregated analytics from multiple properties.

How to use Fleets?

Run the server locally via npx -y fleets-mcp (stdio transport). It pairs with the fleets CLI for configuration and authentication. No further setup or configuration commands are documented in the README.

Key features of Fleets

• Read-only multi-site analytics for AI agents
• Supports GA4, Search Console, Cloudflare edge, and PageSpeed
• Returns paste-ready fixes from audits
• Local stdio server via npx
• Pairs with the fleets CLI tool

Use cases of Fleets

• AI agents querying analytics across all sites they manage
• Automating performance audits and receiving actionable fixes
• Centralizing access to GA4 and Search Console data for multiple properties
• Combining Cloudflare edge metrics with PageSpeed insights

FAQ from Fleets

What data sources does Fleets support?

GA4, Search Console, Cloudflare edge, and PageSpeed. All access is read-only.

How do I run the Fleets server?

Use npx -y fleets-mcp on the command line. It runs as a local stdio MCP server.

Does Fleets require a separate configuration tool?

It pairs with the fleets CLI, which handles authentication and setup. The README does not detail additional configuration steps.

What transport protocol does Fleets use?

The server uses stdio transport, as indicated by the npx invocation and its local MCP server nature.

Is Fleets for individual sites or multiple sites?

It is designed for “every site you run,” aggregating analytics across multiple properties.