Build vs PageSpeed Insights MCP
A side-by-side look at the Build and PageSpeed Insights MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Build for developer tools work as a local process; choose PageSpeed Insights MCP for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Build when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose PageSpeed Insights MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You want tools like
analyse_page, get_field_data, explain_lcp.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 139 | 1 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Build | View PageSpeed Insights MCP |
Tools & capabilities
Build tools
No tool names declared yet. Check the project README from the listing page.
PageSpeed Insights MCP tools 6
analyse_pageEverything in one call, and the one most people want. Scores with their spread, what is failing ranked by what fixing it is worth, real-user data if Google has any, and a self-contained HTML page to save or forward. Only a fault that failed in every analysis counts, because audits are as noisy as s…get_field_dataReal-user data from the Chrome UX Report. One call, answers at once. `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.compare_to_baselineDid 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.get_job_resultCollects 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.check_setupWhether the key works, whether the Chrome UX Report is reachable, and which baselines are held, without disclosing the key.
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.
Build
{
"mcpServers": {
"build": {
"command": "npx",
"args": [
"-y",
"@paretools/init"
]
}
}
}
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.
Frequently asked questions
Build is categorized under Developer Tools and uses a local stdio subprocess. PageSpeed Insights MCP belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Build for developer tools work and PageSpeed Insights MCP for developer tools.
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.
Build is listed as free. Auth: no auth required. PageSpeed Insights MCP has no declared pricing — check the project's own site. 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 build and pagespeed-insights-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Build has a quality signal of 51/100 (Good) with 5 views, 0 installs and 139 GitHub stars. PageSpeed Insights MCP has 45/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.