PageSpeed Insights MCP vs Claude Flow
A side-by-side look at the PageSpeed Insights MCP and Claude Flow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PageSpeed Insights MCP for developer tools work; choose Claude Flow for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose PageSpeed Insights MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You want tools like
report, check_pagespeed, diagnose_page.
Choose Claude Flow when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Coding Agents |
| Quality signal | 45/100 · Fair | 49/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 79,057 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View PageSpeed Insights MCP | View Claude Flow |
Tools & capabilities
PageSpeed Insights MCP tools 8
reportEverything in one call, and the one most people want. Scores with their spread, real-user data if Google has any, and what is failing ranked by what fixing it is worth. Returns a self-contained HTML page as well, to save or forward. Comes back as a job id.check_pagespeedScores only. Median of N distinct analyses with the spread. `urls`, `strategy` (mobile, desktop or both), `runs` (1-10, default 5). Anything past a single analysis comes back as a job id.diagnose_pageWhat is failing, ranked. Only reports a fault that failed in every analysis, because audits are as noisy as scores. Comes back as a job id.field_dataReal-user data from the Chrome UX Report. `urls`, and `history` for the weekly p75 series.explain_lcpWhich of four phases owns a slow Largest Contentful Paint: server response, the wait before the browser starts fetching the largest image, the download, then the wait before it is painted. One call, answers at once.compareDid the change actually help. Measures now and compares against a saved baseline, giving a verdict only where the two ranges do not overlap. Comes back as a job id.check_statusCollects a measurement that was handed back as a job id. Answers immediately, every time. `job_id`, or nothing at all for the most recent one.diagnoseWhether the key works, whether the Chrome UX Report is reachable, and which baselines are held, without disclosing the key.
Claude Flow tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
PageSpeed Insights MCP
No confirmed install command for PageSpeed Insights MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Claude Flow
{
"mcpServers": {
"claude-flow": {
"command": "npx",
"args": [
"-y",
"ruflo@latest"
]
}
}
}
Frequently asked questions
PageSpeed Insights MCP is categorized under Developer Tools and uses an install path we have not confirmed yet. Claude Flow belongs to Coding Agents and uses a local stdio subprocess. Pick PageSpeed Insights MCP for developer tools work and Claude Flow for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. PageSpeed Insights MCP has no confirmed install command yet — follow its own setup instructions.
PageSpeed Insights MCP has no declared pricing — check the project's own site. Claude Flow has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add pagespeed-insights-mcp and claude-flow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PageSpeed Insights MCP has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Claude Flow has 49/100 (Fair) with 3 views, 0 installs and 79,057 GitHub stars.