OctoBoost SEO MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OctoBoost SEO MCP Server run an SEO audit on my homepage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OctoBoost SEO MCP Server
Expose the OctoBoost SEO API as Model Context Protocol (MCP) tools so agents can audit websites with compact, structured results instead of fetching and parsing raw HTML.
Get your free API key at octo-boost.com. New accounts include free credits to try every tool.
What This Server Does
octoboost-mcp-server gives an MCP client three core capabilities:
discover available analyzers with
list_analyzerscrawl a domain for relevant URLs with
scan_domainrun full audits with
analyze
It is built for agent workflows that need SEO and AI-visibility signals inside the reasoning loop without spending thousands of tokens on raw page content.
Related MCP server: SEO Screaming Toad MCP Server
Who It's For
This server is a good fit for:
developers building MCP-enabled products, assistants, or internal automation
teams using MCP clients such as Cursor or Claude Desktop and wanting SEO tooling via config only
AI agent workflows that need token-efficient site audits, progress updates, and structured outputs they can reason over
It is less useful if you want a general SEO learning guide or a raw HTML scraping tool. The main value here is compact audit output for automated workflows.
Why Use This Instead Of Raw Scraping?
Running SEO checks directly in an LLM context is expensive. OctoBoost moves the heavy lifting to the API and returns only the signals an agent needs to decide what to do next.
Token-efficient: structured results instead of raw HTML
LLM-friendly: scores, flags, and diagnostics instead of prose parsing
Credit-aware: responses include credits used and credits remaining
Predictable errors:
401for invalid or expired keys,402for exhausted credits
Quick Start
Get an API key from octo-boost.com.
Add the server to your MCP client config.
Call
list_analyzersto verify the connection.
{
"mcpServers": {
"octoboost-seo": {
"command": "npx",
"args": ["-y", "octoboost-mcp-server"],
"env": {
"OCTOBOOST_API_KEY": "your-api-key"
}
}
}
}Common config locations:
Claude Desktop:
~/Library/Application Support/Claude/claude_desktop_config.jsonCursor: Cursor MCP settings
OpenClaw:
~/.openclaw/mcp.json
Core Workflow
Most agent flows follow this pattern:
1. list_analyzers
-> learn categories and available checks
2. scan_domain { domain: "acme.com" }
-> collect relevant URLs for the audit
3. analyze { urls: [...] }
-> run a full audit with SEO score + GEO/AEO score for each URLTools Overview
list_analyzers
Returns available analyzer keys, categories, and weights. Call this first so an agent knows what it can run.
no input required
current categories include
seo,accessibility,ux,performance, andgeoweights returned reflect your personal setup (see Analysis Setup below)
scan_domain
Crawls a domain and returns SEO-relevant URLs.
Parameter | Type | Default | Description |
| string | — | Domain or URL to scan |
| number | server default | Maximum pages to crawl (capped server-side at the batch analysis limit) |
| string[] |
| URL patterns to skip |
| boolean |
| Honor |
| boolean |
| Skip alternate-language duplicates |
analyze
Runs a full audit for one or more URLs. All 30+ analyzers run on each URL, returning an overall SEO score, per-category scores, and a GEO/AEO score for AI search visibility. URLs are processed sequentially and emit progress notifications after each one.
Parameter | Type | Description |
| string[] | URLs to analyze |
Cost: 3 credits per URL.
Analysis Setup
From your dashboard at octo-boost.com/dashboard, you can configure how much each analyzer contributes to the overall score. Set a weight between 0 and 5 for any of the 30+ analyzers.
Weight 0 — the analyzer still runs but is excluded from the overall score calculation
Weight 1–5 — higher values give an analyzer more influence over the final score
Changes apply immediately to all future API calls made with your key
list_analyzersalways returns your current weights, so agents can adapt their reasoning to your setup
Core Web Vitals (CrUX)
Full audits include real-user performance data (LCP, CLS, INP, FCP, TTFB) from the Chrome UX Report API at the p75 percentile — the speed 75% of actual Chrome users experienced or better. Google uses these as Search ranking signals.
If no data is returned, the result includes the exact reason (e.g. insufficient traffic, URL not in Google's dataset). This is common for low-traffic sites and does not affect the overall SEO score.
GEO/AEO Output
Full audits include a geoScore alongside the technical SEO score.
This score is meant for AI-search and agent workflows. It helps answer whether a page is easy for systems like ChatGPT, Claude, Gemini, or Perplexity to understand, extract, retrieve, and cite.
Key fields include:
geoScoretechnicalAccesscontentStructureentityClarityauthoritySignalscitationLikelihoodragReadinessllmAssessmentwhyThisMattersForAgents
Project Status
Planned next:
LLM-based prioritization and condensation for more compact output
higher-level tools such as
get_fix_plan,summarize_top_opportunitiesandcompare_urlsbetter site-level workflows built on top of crawl plus analysis
dedicated interface and API documentation
Available Tools
4 toolsanalyzeA
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.
Inputs: urls (required).
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.
Inputs: url, page, analyzer, category.
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.
Inputs: no named parameters.
scan_domainA
Crawl a domain and return all SEO-relevant page URLs. Use this to discover pages before running analysis.
Inputs: domain (required), maxPages, excludePatterns, respectRobotsTxt, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Your agent needs to crawl a site and say what is wrong with it — broken tags, duplicate content, pages nothing can index, resources that never load. **What you can ask for** • "Crawl this site and list every page with a duplicate title or missing description." • "Which pages are non-indexable, and why?" • "Run Lighthouse on these URLs and give me the failing audits." • "Show the internal link graph and the orphan pages." • "Give me this page's raw HTML and its microdata." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-onpage/mcp and sign in with OAuth — there is no key to create or paste. 20 tools: submit a crawl and read its summary, pages, resources, links and waterfall; duplicate content and duplicate tags; keyword density; non-indexable and uncrawlable resources; parsed content, raw HTML, microdata, screenshots and Lighthouse. **Why this rather than the source** A crawler you drive from the agent, with the audit results as structured data rather than a PDF. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the broken pages here, then ask the same agent what those pages used to rank for — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Live SEO intelligence, rank tracking, site audits, and backlink analysis for AI agents.
SEO & marketing toolkit for AI agents: GA4, Search Console, AdSense, GTM, PageSpeed, Trends.
Audit, rank-track and analyze SEO for sites via an authenticated MCP server.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to perform comprehensive SEO audits on web pages, including meta tags, headings, links, images, performance, and more, via a CLI or MCP server.181MIT
- AlicenseNot gradedqualityDmaintenanceProvides 23 bounded MCP tools for AI agents to perform technical SEO audits, including crawl setup, page analysis, issue detection, and report exports, all while keeping data local.7MIT
- AlicenseAqualityCmaintenanceProvides on-page SEO analysis via MCP tools, including page audits, schema extraction, robots.txt checks, sitemap parsing, and link analysis. No API keys required; works with any MCP-compatible client.520 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to audit URLs or raw HTML for SEO, AEO, and GEO performance, generate llms.txt manifests, and check the tool version via MCP tools.1MIT