<!-- Updated: 2026-02-07 -->
Scanned 5/31/2026
Install via CLI
openskills install tools-only/X-Skills<!-- Updated: 2026-02-07 -->
# MCP Integration
## Overview
Claude SEO can integrate with Model Context Protocol (MCP) servers to access external APIs and enhance analysis capabilities.
## Available Integrations
### PageSpeed Insights API
Use Google's PageSpeed Insights API directly for real Core Web Vitals data.
**Configuration:**
1. Get an API key from [Google Cloud Console](https://console.cloud.google.com/)
2. Enable the PageSpeed Insights API
3. Use in your analysis:
```bash
curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=URL&key=YOUR_API_KEY"
```
### Google Search Console
For organic search data, use the `mcp-server-gsc` MCP server by [ahonn](https://github.com/ahonn/mcp-server-gsc). Provides search performance data, URL inspection, and sitemap management.
**Configuration:**
```json
{
"mcpServers": {
"google-search-console": {
"command": "npx",
"args": ["-y", "mcp-server-gsc"],
"env": {
"GOOGLE_CREDENTIALS_PATH": "/path/to/credentials.json"
}
}
}
}
```
### PageSpeed Insights MCP Server
Use `mcp-server-pagespeed` by [enemyrr](https://github.com/enemyrr/mcp-server-pagespeed) for Lighthouse audits, CWV metrics, and performance scoring via MCP.
**Configuration:**
```json
{
"mcpServers": {
"pagespeed": {
"command": "npx",
"args": ["-y", "mcp-server-pagespeed"],
"env": {
"PAGESPEED_API_KEY": "your-api-key"
}
}
}
}
```
### Official SEO MCP Servers (2025-2026)
The MCP ecosystem for SEO has matured significantly. These are production-ready integrations:
| Tool | Package / Endpoint | Type | Notes |
|------|-------------------|------|-------|
| **Ahrefs** | `@ahrefs/mcp` | Official | Launched July 2025. Supports local and remote modes. Backlinks, keywords, site audit data. |
| **Semrush** | `https://mcp.semrush.com/v1/mcp` | Official (remote) | Full API access via remote MCP endpoint. Domain analytics, keyword research, backlink data. |
| **Google Search Console** | `mcp-server-gsc` | Community | By ahonn. Search performance, URL inspection, sitemaps. |
| **PageSpeed Insights** | `mcp-server-pagespeed` | Community | By enemyrr. Lighthouse audits, CWV metrics, performance scoring. |
| **DataForSEO** | `dataforseo-mcp-server` | Community | By Skobyn (GitHub: Skobyn/dataforseo-mcp-server). SERP data, keyword data, backlinks. |
| **kwrds.ai** | kwrds MCP server | Community | Keyword research, search volume, difficulty scoring. |
| **SEO Review Tools** | SEO Review Tools MCP | Community | Site auditing and on-page analysis API. |
## API Usage Examples
### PageSpeed Insights
```python
import requests
def get_pagespeed_data(url: str, api_key: str) -> dict:
"""Fetch PageSpeed Insights data for a URL."""
endpoint = "https://www.googleapis.com/pagespeedonline/v5/runPagespeed"
params = {
"url": url,
"key": api_key,
"strategy": "mobile", # or "desktop"
"category": ["performance", "accessibility", "best-practices", "seo"]
}
response = requests.get(endpoint, params=params)
return response.json()
```
### Core Web Vitals from CrUX
```python
def get_crux_data(url: str, api_key: str) -> dict:
"""Fetch Chrome UX Report data for a URL."""
endpoint = "https://chromeuxreport.googleapis.com/v1/records:queryRecord"
payload = {
"url": url,
"formFactor": "PHONE" # or "DESKTOP"
}
headers = {"Content-Type": "application/json"}
params = {"key": api_key}
response = requests.post(endpoint, json=payload, headers=headers, params=params)
return response.json()
```
## Metrics Available
### From PageSpeed Insights
| Metric | Description |
|--------|-------------|
| LCP | Largest Contentful Paint (lab) |
| INP | Interaction to Next Paint (estimated) |
| CLS | Cumulative Layout Shift (lab) |
| FCP | First Contentful Paint |
| TBT | Total Blocking Time |
| Speed Index | Visual progress speed |
### From CrUX (Field Data)
| Metric | Description |
|--------|-------------|
| LCP | 75th percentile, real users |
| INP | 75th percentile, real users |
| CLS | 75th percentile, real users |
| TTFB | Time to First Byte |
## Best Practices
1. **Rate Limiting**: Respect API quotas (typically 25k requests/day for PageSpeed)
2. **Caching**: Cache results to avoid redundant API calls
3. **Field vs Lab**: Prioritize field data (CrUX) for ranking signals
4. **Error Handling**: Handle API errors gracefully
## Without API Keys
If you don't have API keys, Claude SEO can still:
1. Analyze HTML source for potential issues
2. Identify common performance problems
3. Check for render-blocking resources
4. Evaluate image optimization opportunities
5. Detect JavaScript-heavy implementations
The analysis will note that actual Core Web Vitals measurements require field data from real users.
No comments yet. Be the first to comment!