MCP Server Pagespeed
# @enemyrr/mcp-server-pagespeed
A Model Context Protocol server that provides Google PageSpeed Insights analysis. This server enables AI models to analyze webpage performance through a standardized interface.
<a href="https://glama.ai/mcp/servers/wes81w8il2"><img width="380" height="200" src="https://glama.ai/mcp/servers/wes81w8il2/badge" alt="Server Pagespeed MCP server" /></a>
## Installation & Setup for Cursor IDE
1. Clone and build the project:
```bash
git clone https://github.com/enemyrr/mcp-server-pagespeed.git
cd mcp-server-pagespeed
npm install
npm run build
```
2. Add the server in Cursor IDE settings:
- Open Command Palette (Cmd/Ctrl + Shift + P)
- Search for "MCP: Add Server"
- Fill in the fields:
- Name: `pagespeed`
- Type: `command`
- Command: `node /absolute/path/to/mcp-server-pagespeed/build/index.js`
> **Note**: Replace `/absolute/path/to/` with the actual path where you cloned and built the project.
## Command-line Usage
Just run:
```bash
npx mcp-server-pagespeed
```
## Available Tools
### analyze_pagespeed
Analyze a webpage using Google PageSpeed Insights API.
```typescript
use_mcp_tool({
server_name: "pagespeed",
tool_name: "analyze_pagespeed",
arguments: {
url: "https://example.com"
}
});
```
The tool returns:
- Overall performance score (0-100)
- Loading experience metrics
- First Contentful Paint
- First Input Delay
- Top 5 improvement suggestions with:
- Title
- Description
- Potential impact
- Current value
## Features
- Real-time webpage performance analysis
- Detailed loading experience metrics
- Prioritized improvement suggestions
- Comprehensive error handling
- TypeScript support
## Error Handling
The server provides detailed error messages for:
- Invalid URLs
- API request failures
- Connection issues
- Invalid tool calls
## Contributing
Contributions are welcome! Please feel free to submit a Pull Request to https://github.com/enemyrr/mcp-server-pagespeed
## License
MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (analyze_pagespeed). Since there is only one tool, consistency is inherently perfect with no deviations to assess.
A single tool is too few for a server named 'MCP Server Pagespeed', which suggests a broader scope for page speed analysis. This minimal set feels thin and limits functionality, as it only covers analysis without supporting operations like history tracking or batch processing.
The tool surface is severely incomplete for a page speed analysis domain. It only provides analysis but lacks essential operations such as retrieving historical results, comparing analyses, or managing configurations, leaving significant gaps for agent workflows.