In-depth architectural comparison of the Hub MCP and PageSpeed Insights MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Hub MCP
Developer Tools · Remote HTTP/SSE
Quality: 77/100 (Great) | Auth: API Key required
PageSpeed Insights MCP
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Hub MCP if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose PageSpeed Insights MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Hub MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.
Hub MCP is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, PageSpeed Insights MCP belongs to Developer Tools using local stdio subprocess. Select Hub MCP when you need capabilities focused on developer tools and PageSpeed Insights MCP when you require tools for developer tools.
Number of documents to skip for pagination (number, optional)
images
Filter on image names (string, optional)
operating_systems
Filter on operating systems (string, optional)
order
Change the ordering of results (string, optional)
size
Maximum number of results to return (number, optional)
sort
Sort results by search field (string, optional)
+23 more tools listed on main page
PageSpeed Insights MCP Tools (8)
report
Everything 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_pagespeed
Scores 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_page
What 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_data
Real-user data from the Chrome UX Report. `urls`, and `history` for the weekly p75 series.
explain_lcp
Which 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
Did 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_status
Collects 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.
diagnose
Whether the key works, whether the Chrome UX Report is reachable, and which baselines are held, without disclosing the key.