Skip to main content
Glama
Sign In

PageSpeed Insights MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted PageSpeed Insights MCP server, with each action switched on or off per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/pagespeed-mcp-server
GitHub Stars
0
Server Listing
PageSpeed Insights MCP Server
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation2/5

execute_action and query_data are described almost identically: both are labeled 'Step 3 FINAL' for executing PageSpeed Insights queries, with the same body schema (action, workspace_id, url, strategy, categories, locale). An agent cannot reliably tell which one to call. prompts_menu and query_contexts are clearly distinct, but the core pair is ambiguous.

Naming Consistency4/5

All names use snake_case: execute_action, prompts_menu, query_contexts, query_data. The only minor deviation is the query_* prefix on two tools versus execute_/noun forms, but all are readable and follow a predictable convention.

Tool Count3/5

Four tools is thin for a full PageSpeed Insights integration, and two of the four appear to be duplicates. Effectively there are three functional tools (context helper, prompt catalog, execution), which feels minimal but not extreme.

Completeness3/5

The generic action execution model can cover many analysis types (full analysis, core web vitals, resource audits), and query_contexts provides discovery. However, there is no tool for retrieving past reports, comparing runs over time, or listing previous analyses, and the duplicated execution path creates dead-end confusion rather than coverage.

Available Tools

4 tools
execute_actionPageSpeed Analysis Execute ActionA
Destructive
Inspect

Execute PageSpeed Insights actions (Step 3 FINAL).

Prerequisites: Run query_contexts with request='accounts' (includes available_actions) + request='actions_details' to understand the required payload.

IMPORTANT: The 'body' parameter is a dictionary that must contain ALL fields including:

  • action: Action name (e.g. 'analyze.full', 'core-web-vitals', 'audits.resource-optimizations')

  • workspace_id: Integer workspace ID

  • url: The URL to analyze (required)

  • strategy: 'mobile' or 'desktop' (default: mobile)

  • categories: Optional list of categories ['performance', 'accessibility', 'best-practices', 'seo']

  • locale: Optional language code (e.g., 'en-US')

Do NOT pass these as separate parameters - they must ALL be inside the body dictionary.

Inputs: body (required). Returns: object

prompts_menuPageSpeed PromptsB
Read-only
Inspect

Browse the PageSpeed Insights prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsPageSpeed Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe PageSpeed Insights queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all actions you can query).

Step 2: request='actions_details' with actions=['analyze.full', 'core-web-vitals'] – REQUIRED before querying. Returns the exact request body, required parameters, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataPageSpeed Analysis QueryA
Read-only
Inspect

Execute PageSpeed Insights analysis queries (Step 3 FINAL).

Prerequisites: Run query_contexts with request='accounts' (includes available_actions) + request='actions_details' to understand the required payload.

IMPORTANT: The 'body' parameter is a dictionary that must contain ALL fields including:

  • action: Action name (e.g. 'analyze.full', 'core-web-vitals', 'audits.resource-optimizations')

  • workspace_id: Integer workspace ID

  • url: The URL to analyze (required)

  • strategy: 'mobile' or 'desktop' (default: mobile)

  • categories: Optional list of categories ['performance', 'accessibility', 'best-practices', 'seo']

  • locale: Optional language code (e.g., 'en-US')

Do NOT pass these as separate parameters - they must ALL be inside the body dictionary.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • page-speed-insights-mcp

      Sivakumar-intoaec
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps the Google PageSpeed Insights API to analyse web performance, providing tools for scores, Core Web Vitals, opportunities, diagnostics, and batch analysis.
      -

    • pagespeed-insights-mcp

      damijanc
      A
      license
      Not graded
      quality
      D
      maintenance
      This MCP server integrates Google PageSpeed Insights to analyze website performance, accessibility, best practices, SEO, and PWA on mobile and desktop, returning detailed audits and optimization opportunities.
      MIT
    • Jepto MCP

      Jepto MCPofficial

      jepto
      A
      license
      Not graded
      quality
      B
      maintenance
      A hosted remote MCP server that connects marketing platforms such as Google Ads, GA4, Search Console, Meta Ads, Microsoft Ads, LinkedIn Ads, TikTok Ads, and Google Business Profile, enabling plain-English performance analysis, KPI and budget tracking, report creation, and previewed account changes.
      8
      MIT

    • multi-site-monitor

      faisibash-oss
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that pulls PageSpeed Insights and Google Search Console data across multiple owned sites, enabling cross-site performance reports and synthesis via Claude.
      MIT
    Try in Browser
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources