SEO Crawler MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Set to "true" to enable verbose debug logging | false |
| OUTPUT_DIR | Yes | Directory where crawl results are saved |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_seo_auditB | Crawl a website and extract comprehensive SEO data using Crawlee HttpCrawler. Returns crawl ID and output path. |
| analyze_seoB | Analyze SEO data from a completed crawl. Runs 25+ SQL queries to detect critical issues, content problems, technical SEO issues, security vulnerabilities, and optimization opportunities. Returns structured report with affected URLs and fix recommendations. |
| query_seo_dataA | Execute a specific SEO analysis query by name. Use list_seo_queries to see available queries. Returns detailed results with affected URLs and context. |
| list_seo_queriesB | List all available SEO analysis queries with descriptions, priorities, and fix recommendations. Optionally filter by category or priority level. |
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 4 tools
The tools have mostly distinct purposes, but there is some overlap between analyze_seo and query_seo_data, as both involve executing SEO analysis queries. However, analyze_seo runs a predefined set of queries, while query_seo_data allows for executing specific queries by name, which helps differentiate them. The other tools (list_seo_queries and run_seo_audit) are clearly distinct.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., analyze_seo, list_seo_queries, query_seo_data, run_seo_audit). The naming is predictable and readable, with no deviations in style or convention.
With 4 tools, the count is reasonable for an SEO crawler server, covering key operations like crawling, listing queries, executing queries, and analyzing data. It might be slightly thin for a comprehensive SEO toolset, but it is well-scoped and each tool earns its place.
The toolset covers core SEO analysis workflows, including crawling, query listing, and data analysis. However, there are notable gaps, such as missing update or delete operations for managing queries or crawl data, and no tools for monitoring or reporting beyond the initial analysis. This could limit agent flexibility in handling ongoing SEO tasks.