@enemyrr/mcp-server-pagespeed

Created By
enemyrra year ago
Overview

what is @enemyrr/mcp-server-pagespeed?

@enemyrr/mcp-server-pagespeed is a Model Context Protocol server that provides Google PageSpeed Insights analysis, enabling AI models to analyze webpage performance through a standardized interface.

how to use @enemyrr/mcp-server-pagespeed?

To use the server, clone the repository, build the project, and add it to Cursor IDE settings. You can also run it directly from the command line using npx mcp-server-pagespeed.

key features of @enemyrr/mcp-server-pagespeed?

  • Real-time webpage performance analysis
  • Detailed loading experience metrics
  • Prioritized improvement suggestions
  • Comprehensive error handling
  • TypeScript support

use cases of @enemyrr/mcp-server-pagespeed?

  1. Analyzing webpage performance for SEO optimization.
  2. Identifying loading issues to enhance user experience.
  3. Providing actionable insights for web developers to improve site speed.

FAQ from @enemyrr/mcp-server-pagespeed?

  • What does the analyze_pagespeed tool do?

It analyzes a webpage using the Google PageSpeed Insights API and returns performance scores and improvement suggestions.

  • How do I install the server?

Clone the repository, run npm install, and build the project as per the setup instructions.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can submit a Pull Request on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
enemyrr
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago