SEO/AEO Audit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRUX_API_KEY | No | Google Chrome UX Report API key (optional, free) | |
| AHREFS_API_KEY | Yes | Ahrefs API key (required, paid subscription) | |
| OPENAI_API_KEY | Yes | OpenAI API key (required, paid subscription) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_audit_dataA | Crawl a website and fetch its Ahrefs SEO metrics. Returns a JSON object with: crawl (pages, issues, schema summary), ahrefs (DR, keywords, traffic, backlinks, top pages, referring domains), brand_name (inferred from schema/title), and industry (inferred from page content). Call this first when auditing a site. |
| fetch_ai_visibilityA | Measure how often a brand appears in AI/answer-engine results for unbiased, category-level buyer queries. Generates prompts (brand-name excluded), runs grounded web-search rankings, and returns brand visibility %, average position, per-topic breakdown, and competitor brands. Pass brand and industry from fetch_audit_data when available. Requires OPENAI_API_KEY. |
| render_audit_pdfA | Render the completed SEO/AEO audit report as a PDF file. Pass the ahrefs and crawl objects exactly as returned by fetch_audit_data (pass through unchanged), plus the ai_visibility data you gathered via web search and the narratives you wrote based on the data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: fetch_audit_data crawls websites, fetch_ai_visibility measures AI visibility, and render_audit_pdf generates reports. There is no overlap or ambiguity.
All tools follow a consistent verb_noun pattern (fetch_audit_data, fetch_ai_visibility, render_audit_pdf), making it easy for an agent to infer functionality from names.
With only 3 tools, the server is tightly scoped to its domain. Each tool is necessary and well-justified, avoiding bloat or insufficiency.
The tool set covers the full audit workflow: data collection (fetch_audit_data), AI visibility analysis (fetch_ai_visibility), and report generation (render_audit_pdf). No obvious gaps exist for the stated purpose.