Pagespeed Insights MCP vs Claude Task Master
A side-by-side look at the Pagespeed Insights MCP and Claude Task Master 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 as a local process; choose Claude Task Master for developer tools 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 prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GOOGLE_API_KEY. - You want tools like
pagespeed_analyze_page, pagespeed_diagnose_page, pagespeed_get_field_data.
Choose Claude Task Master when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, OPENROUTER_API_KEY, MISTRAL_API_KEY, TASK_MASTER_TOOLS.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 68/100 · Great | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | BYOK (pay the provider) |
| Required env vars | GOOGLE_API_KEY | ANTHROPIC_API_KEYOPENAI_API_KEYGOOGLE_API_KEYPERPLEXITY_API_KEYXAI_API_KEYOPENROUTER_API_KEYMISTRAL_API_KEYTASK_MASTER_TOOLS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 76 | 28,276 |
| Directory activity | 1 views 0 installs 0 upvotes | 10 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Pagespeed Insights MCP | View Claude Task Master |
Tools & capabilities
Pagespeed Insights MCP tools 6
pagespeed_analyze_pageRun a PageSpeed Insights Lighthouse analysis for one public page. Start with report=summary for a health check; choose full for audits, recommendations for a prioritized fix list, audit for non-performance categories, or performance-map for Mermaid. Example: analyze a mobile product page and return the three most useful remediation steps. Returns a report plus structured result. The Google API is contacted and results may be served from the local cache.pagespeed_diagnose_pageInspect one page through exactly one diagnostic lens: visual, elements, network, javascript, images, render-blocking, or third-parties. Use after pagespeed_analyze_page identifies a problem; do not use it for a general score. Example: focus=render-blocking to identify CSS/JS delaying first render. Returns focused evidence rather than a full Lighthouse dump.pagespeed_get_field_dataGet real-user Core Web Vitals from Chrome UX Report, not Lighthouse lab measurements. Use scope=page for one URL; use scope=origin with a bare origin when the page has insufficient traffic. Example: check mobile LCP and INP for https://example.com/checkout. Returns p75 field metrics or a clear no-data result.pagespeed_compare_pagesCompare two pages now (mode=pages) or measure one page against its locally stored baseline (mode=baseline). Baseline mode records the first call; use runs=3 or more and rely on guaranteed deltas, not medians alone. Example: compare staging against production, or verify whether a deployed fix improved mobile LCP. replaceBaseline overwrites local baseline state.pagespeed_analyze_batchAnalyze 1–10 public URLs and return per-page results plus success/failure counts. Use pagespeed_analyze_page for one URL or pagespeed_compare_pages for a direct comparison. Example: triage the ten highest-traffic landing pages. Progress notifications are emitted when supported by the client.pagespeed_clear_cacheClear only this server process's in-memory PageSpeed response cache, forcing later analysis calls to contact Google again. Use after a deploy when a cached result is stale. It does not change the target website, files, or remote data; repeating the call is safe.
Claude Task Master 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
{
"mcpServers": {
"pagespeed-insights-mcp-2": {
"command": "npx",
"args": [
"-y",
"pagespeed-insights-mcp"
],
"env": {
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE"
}
}
}
}
Claude Task Master
{
"mcpServers": {
"eyaltoledano-claude-task-master": {
"command": "npx",
"args": [
"-y",
"task-master-ai"
],
"env": {
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE",
"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
"XAI_API_KEY": "YOUR_XAI_API_KEY_HERE",
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
"MISTRAL_API_KEY": "YOUR_MISTRAL_API_KEY_HERE",
"TASK_MASTER_TOOLS": "YOUR_TASK_MASTER_TOOLS_HERE"
}
}
}
}
Frequently asked questions
Pagespeed Insights MCP is categorized under Developer Tools and uses a local stdio subprocess. Claude Task Master belongs to Developer Tools and uses a local stdio subprocess. Pick Pagespeed Insights MCP for developer tools work and Claude Task Master 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 is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Claude Task Master is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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-2 and eyaltoledano-claude-task-master 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 68/100 (Great) with 1 views, 0 installs and 76 GitHub stars. Claude Task Master has 60/100 (Good) with 10 views, 0 installs and 28,276 GitHub stars.