Six tools for SEO and AI-readability audits. 91 checks, 11 score modules.
Model Context Protocol server for MetricSpot. Exposes 6 SEO + AI-readability audit tools to AI agents (Claude, ChatGPT, Gemini, Perplexity, Cursor, Zed, OpenClaw, custom bots).
https://mcp.metricspot.com/mcpnpx @metricspot/mcp-server| Tool | Auth | Description |
|---|---|---|
run_audit_anonymous | none | One-shot audit, 1/IP/24h, no Core Web Vitals |
run_audit | Bearer key | Full audit with PSI, returns audit_id |
get_audit | Bearer key | Fetch audit + findings by id |
list_audits | Bearer key | List the user's recent audits (max 100) |
get_audit_pdf | Bearer key | Signed URL for the branded PDF report |
get_organic_traffic | Bearer key | 28-day GA4 + GSC snapshot (if Google linked) |
Claude Code (~/.claude/mcp.json):
{
"mcpServers": {
"metricspot": {
"command": "npx",
"args": ["-y", "@metricspot/mcp-server"],
"env": {
"MCP_API_KEY": "ms_live_xxx"
}
}
}
}
Cursor (~/.cursor/mcp.json) and Zed use the same shape.
Omit MCP_API_KEY to only use run_audit_anonymous.
POST https://mcp.metricspot.com/mcp
Authorization: Bearer ms_live_xxx
Content-Type: application/json
{"jsonrpc":"2.0","id":1,"method":"tools/list"}
| Var | Default | Purpose |
|---|---|---|
PORT | 3000 | HTTP listen port |
APP_API_BASE_URL | https://app.metricspot.com | MetricSpot app API base (the dev/dev:stdio scripts override it to http://localhost:3000) |
APP_PUBLIC_BASE_URL | falls back to APP_API_BASE_URL | Used to build report_url |
MCP_INTERNAL_TOKEN | — | Service-to-service secret forwarded as X-MCP-Internal-Token |
MCP_API_KEY | — | (stdio only) User API key, sent as Authorization: Bearer to the HTTP layer |
bun install
bun run typecheck
bun test
bun run dev # Streamable HTTP on :3000
bun run dev:stdio # stdio loop (send JSON-RPC on stdin)
Multi-stage Dockerfile produces a Bun runtime image. Independent Dokku app on the same Hetzner droplet as app/ and web/.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @metricspot/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-metricspot-seo-mcp": {
"command": "npx",
"args": [
"-y",
"@metricspot/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@metricspot/mcp-servernpmcom.metricspot/seo-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.