SEO MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPSOLVER_API_KEY | Yes | CapSolver API key to solve CAPTCHA |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_backlinks_listA | |
| keyword_generatorC | Get keyword ideas for the specified keyword |
| get_trafficC | |
| keyword_difficultyC | Get keyword difficulty for the specified keyword |
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
Each tool addresses a distinct SEO function: backlinks, traffic, keyword difficulty, and keyword generation. There is no overlap in purpose.
Two tools use the 'get_' prefix (get_backlinks_list, get_traffic) while two do not (keyword_difficulty, keyword_generator). This inconsistency in naming pattern could confuse an agent.
With 4 tools, the set is appropriately scoped for basic SEO tasks. It is not too small or too large for the domain.
Core SEO operations are covered (backlinks, traffic, keywords), but lacks features like rank tracking, site audit, or competitive analysis, leaving notable gaps.