SEO Optimizer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SerpAPI_KEY | No | Optional API key for SerpAPI to get richer SERP data; without it, falls back to DuckDuckGo. | |
| GOOGLE_PAGESPEED_API_KEY | No | Optional API key for Google PageSpeed Insights to raise rate limits; works without a key. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_pageA | Fetch a URL and return cleaned, readable HTML (scripts/styles/attributes stripped). Use for the target page, competitor pages, robots.txt, sitemap.xml, etc. |
| pagespeedB | Google PageSpeed Insights / Lighthouse summary: Core Web Vitals (LCP, CLS, INP, TTFB, FCP) plus the biggest performance opportunities. |
| serpA | Organic search results for a keyword (top ranking URLs, titles, descriptions, positions). Uses SerpAPI if SerpAPI_KEY is set, otherwise falls back to a key-less DuckDuckGo lookup. The "source" field in the output says which was used. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| technical-auditor | Robots, canonical, redirects, schema, indexability. |
| page-speed | Core Web Vitals (LCP, CLS, INP, TTFB) and performance. |
| meta-optimizer | Title, meta description, H1, Open Graph, CTR. |
| internal-link | Orphan pages, anchor text, link depth. |
| semantic-content | Topical completeness and entity coverage. |
| cannibalization | Keyword overlap and intent collisions. |
| competitor-gap | Keyword/content gaps vs. SERP competitors. |
| ai-visibility | AI-search readiness, FAQ schema, llms.txt. |
| company-intelligence | Business model, industry, strategic gaps. |
| feedback-analyzer | Root-cause analysis and systemic patterns. |
| geo | Generative Engine Optimization / AI-citation readiness. |
| blog-writer | Full SEO-optimized HTML article (most expensive). |
| seo-full-analysis | Run every specialist lens, then synthesize a single prioritized SEO report. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clear, non-overlapping purpose: fetch_page retrieves HTML, pagespeed provides performance metrics, and serp fetches search results. No ambiguity.
Names mostly follow verb_noun (fetch_page) but pagespeed is a proper noun and serp is an acronym, causing slight inconsistency. However, they are still readable.
3 tools is reasonable for a focused SEO server, covering core functionalities without being overly minimal or excessive.
Covers essential SEO tasks (page fetch, performance, rankings) but lacks tools for backlinks, keyword suggestions, or site audits, leaving notable gaps.