mcp-server-competitor-content
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level for the server. | |
| SERP_API_KEY | No | API key for the configured SERP provider. | |
| SERP_PROVIDER | No | The SERP provider to use (e.g., serpapi, dataforseo, cse). | |
| RESPECT_ROBOTS_TXT | No | Whether to respect robots.txt. | |
| RATE_LIMIT_DELAY_MS | No | Delay between requests in milliseconds. | |
| ENABLE_HEADLESS_FALLBACK | No | Enable Playwright fallback for thin SPA HTML. | |
| ROBOTS_CACHE_TTL_SECONDS | No | TTL for cached robots.txt rules. | |
| HEADLESS_MIN_CONTENT_CHARS | No | Minimum content length for static body before fallback to headless. |
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 |
|---|---|
| scrape_pageA | Fetch and extract clean article body, headings, meta, links, and schema signals from a URL (headless fallback for thin SPA HTML). |
| extract_keywordsB | Extract TF-IDF keywords and bigrams from a URL or raw text. |
| content_gap_analysisA | Compare your content (URL or raw_text) against competitor URLs to find missing keywords, heading gaps, and similarity scores. |
| compare_headingsC | Diff H1–H6 outlines across multiple competitor URLs. |
| readability_scoreC | Flesch-Kincaid, SMOG, and Coleman-Liau readability metrics for a URL or raw text. |
| content_quality_scoreB | Score content quality: word count, links, media, schema, meta, headings. |
| serp_featuresA | Detect featured snippets, PAA, related searches, and organic results via configured SERP API (never scrapes Google directly). |
| cluster_competitorsB | Group competitor pages by TF-IDF cosine similarity (embeddings optional via config). |
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 8 tools
Each tool targets a distinct aspect of competitor content analysis: scraping, keyword extraction, heading comparison, gap analysis, readability, quality scoring, SERP features, and clustering. The boundaries are clear, with content_gap_analysis serving as a higher-level composite rather than overlapping with the lower-level tools.
All names use snake_case and are descriptive, but patterns are mixed: some follow verb_noun (scrape_page, extract_keywords, cluster_competitors) while others are noun_noun (content_gap_analysis, readability_score, serp_features). This is still readable and predictable, but not a single consistent verb-first convention.
Eight tools is well-scoped for the server's purpose. Each tool covers a meaningful step in competitor content analysis without unnecessary redundancy or feature bloat.
The surface covers the core workflow: fetch competitor content, extract and compare keywords/headings, assess readability and quality, detect SERP features, and cluster competitors. No critical operations are missing for the stated domain.