advanced-seo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPSOLVER_API_KEY | Yes | Required for Ahrefs Tools (Backlinks, Keywords, Traffic). Get key from https://dashboard.capsolver.com/ | |
| GOOGLE_PSI_API_KEY | Yes | Required for PageSpeed Insights. Get key from https://developers.google.com/speed/docs/insights/v5/get-started |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_audit_reportA | Generates a full SEO audit report (Markdown) and saves it locally. Combines On-Page, Technical, Ahrefs data into a single file. |
| analyze_page_speedA | Analyzes site speed using Google PageSpeed Insights. Requires GOOGLE_PSI_API_KEY in .env. |
| check_schema_markupB | Validates JSON-LD Schema Markup on a page. |
| check_broken_links_on_pageB | Scans a page for broken links (404s). |
| analyze_content_densityC | Analyzes keyword density and TF-IDF metrics. |
| compare_competitorsA | Compares SEO metrics (Backlinks, Traffic, DR) of two domains. Requires CAPSOLVER_API_KEY. |
| bulk_sitemap_auditA | Scans the sitemap and runs On-Page audit on multiple pages. Useful for finding site-wide issues (e.g., missing H1s). |
| onpage_auditA | Performs a detailed on-page SEO audit of a specific URL. Checks meta tags, heading structure, word count, internal/external links, and image alt tags. Does NOT require an API key. |
| technical_health_checkA | Checks technical SEO aspects of a domain/URL. Verifies robots.txt, sitemap.xml, and security headers (HTTPS, HSTS). Does NOT require an API key. |
| get_backlinksA | Retrieves backlink data for a domain using Ahrefs (Requires CAPSOLVER_API_KEY). Returns domain rating, total backlinks, and a list of top referring pages. |
| keyword_ideasA | Generates keyword ideas and questions based on a seed keyword (Requires CAPSOLVER_API_KEY). |
| estimate_trafficB | Estimates monthly search traffic and value for a domain (Requires CAPSOLVER_API_KEY). |
| check_difficultyB | Checks keyword difficulty and returns SERP analysis (Requires CAPSOLVER_API_KEY). |
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 13 tools
Each tool has a clearly distinct purpose, covering different SEO aspects like keyword analysis, page speed, broken links, schema, competitors, traffic estimates, backlinks, on-page audits, technical checks, and report generation. No two tools appear to do the same thing.
Most tool names follow a verb_noun pattern (e.g., analyze_content_density, check_broken_links_on_page, get_backlinks), but a few deviate (e.g., keyword_ideas, onpage_audit). All use snake_case, so the inconsistency is minor.
With 13 tools, the server covers a broad range of SEO functionality without being bloated. Each tool serves a specific need, and the count is well-suited for an advanced SEO tool set.
The tool set covers key SEO areas: keyword research, on-page auditing, technical SEO, backlinks, competitors, and reporting. Minor gaps like mobile-friendliness or rich results testing exist, but the coverage is very strong overall.