OctoBoost SEO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OCTOBOOST_API_KEY | Yes | Your API key for OctoBoost SEO API |
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 |
|---|---|
| list_analyzersA | List all available SEO analyzers with their keys, categories, and weights. Call this first to discover what analyzers and categories are available before running an analysis. |
| scan_domainA | Crawl a domain and return all SEO-relevant page URLs. Use this to discover pages before running analysis. |
| analyzeA | Analyze one or more URLs for SEO issues. Runs all analyzers and returns scores, issues, and a GEO/AEO score measuring AI search visibility (citation likelihood, RAG readiness, and sub-metrics for technical access, content structure, entity clarity, and authority signals). Processes URLs sequentially and reports progress after each. Costs 3 credits per URL. |
| get_stored_analysisA | Retrieve previously stored SEO analysis reports. No credits consumed. Supports filtering by URL, category, or single analyzer key. Returns paginated results (10 per page). Use this to review past analyses without re-crawling. |
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 has a clear, non-overlapping purpose: analyze runs analyses, get_stored_analysis retrieves past results, list_analyzers shows available options, and scan_domain discovers URLs. No ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case, e.g., get_stored_analysis, list_analyzers. The analyze tool is slightly terse but fits the pattern.
Four tools is appropriate for a focused SEO server. Each tool is essential and covers the core workflow without unnecessary bloat.
The server covers the main SEO analysis flow: scanning, analyzing, retrieving, and listing. Minor gaps exist, such as missing a tool to delete stored analyses, but core functionality is complete.