PluginBench
MCP Server
Maintained
MIT

Stobo SEO & AEO Audit MCP Server

io.github.stobo-app/seo-audit

AI-powered SEO and AEO audit for websites — now retired as of May 2026.

What is the Stobo SEO & AEO Audit MCP server?

The Stobo SEO & AEO Audit MCP server is a retired service that previously provided comprehensive SEO, AEO, and E-E-A-T audits for websites. As of May 2026, the Stobo API has been shut down and the server now exposes only a status tool reporting the retirement; published versions remain available for archival purposes only.

Stobo was designed to audit websites for SEO, AEO (Answer Engine Optimization), and E-E-A-T compliance in a single efficient call, generating structured fix briefs for developers. The service is no longer operational, but the MCP server package remains installable for reference.

How to install Stobo SEO & AEO Audit

Copy-paste configuration for popular MCP clients.

transport: stdio
Config generated by PluginBench — verify against the source before use.
Environment / auth
  • STOBO_API_KEY
    secret

    API key from trystobo.com (optional — free tools work without it)

  • STOBO_BASE_URL

    API base URL (default: https://api.trystobo.com)

~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "seo-audit": {
      "command": "uvx",
      "args": [
        "stobo-mcp"
      ],
      "env": {
        "STOBO_API_KEY": "<YOUR_STOBO_API_KEY>",
        "STOBO_BASE_URL": "<YOUR_STOBO_BASE_URL>"
      }
    }
  }
}

Tools & capabilities

Tools this server exposes to the agent.

  • stobo_status — Reports the retirement of the Stobo service and that the API is no longer available.
  • audit_site — (Retired) Previously performed 30+ SEO and AEO checks across an entire website with E-E-A-T analysis.
  • audit_article — (Retired) Previously performed 7 SEO and 14 AEO checks on a single article.
  • generate_fix_brief — (Retired) Previously generated structured markdown fix briefs from completed audits with prioritized tasks.
  • audit_freshness — (Retired) Previously scanned sitemaps for datePublished and dateModified coverage.
  • generate_robots_txt — (Retired) Previously generated AI-crawler-friendly robots.txt files.
  • generate_sitemap — (Retired) Previously crawled up to 200 URLs and generated sitemap.xml.
  • generate_freshness_code — (Retired) Previously generated JSON-LD snippets with publication and modification dates.
  • check_connection — Diagnostic ping tool that reports service retirement status.

Use cases

  • Audit websites for SEO compliance and search engine optimization (service retired)
  • Analyze article content for AEO (Answer Engine Optimization) readiness (service retired)
  • Generate structured fix briefs for developers to implement audit recommendations (service retired)
  • Check content freshness across sitemaps using datePublished and dateModified metadata (service retired)
  • Generate robots.txt and sitemap files optimized for crawler access (service retired)

Stobo SEO & AEO Audit MCP server FAQ

What is the Stobo SEO & AEO Audit MCP server?

Stobo was an AI-powered audit service that analyzed websites for SEO, AEO, and E-E-A-T compliance. It has been retired as of May 2026 and the API is no longer available. The MCP server now only exposes a status tool.

Is this service still available?

No. The Stobo service was shut down in May 2026. The API is no longer operational and audits cannot be performed.

Can I still install the package?

Yes, published versions remain installable via pip (stobo-mcp) for archival purposes, but the service will not function.

What tools does it expose now?

The retired server exposes a single stobo_status tool that reports the service retirement. Previously available tools like audit_site, audit_article, and generate_fix_brief no longer function.

Do I need an API key?

No API key is required, as the service is no longer operational.

Where can I find alternatives?

The README recommends using web_fetch for manual SEO analysis, though it requires significantly more tokens and cannot compute server-side metrics like Core Web Vitals.

README (reference)

Source of truth, from the repository.

<!-- mcp-name: io.github.stobo-app/seo-audit --> <!-- docs: https://docs.trystobo.com -->

Stobo MCP Server

⚠️ Retired (May 2026). The Stobo SEO/AEO audit service has been shut down and its API is no longer available. This MCP server no longer performs audits — it exposes a single stobo_status tool that reports the retirement and nothing else. Published versions remain installable for archival purposes only. Thank you to everyone who used it.

Audit any site for SEO, AEO, and E-E-A-T from Claude Desktop. Get a structured fix brief your developer can drop straight into Claude Code, Cursor, or VS Code and start shipping.

You: stobo this site: example.com

Claude: I just received a complete audit for example.com. SEO, AEO, EEAT,
per-page breakdowns, 30+ checks with scores and details.

Want me to generate a fix brief you can download and drop into
Claude Code, Cursor, or hand off to your developer?

Why not just use web_fetch?

Fetching every page manually costs ~386,000 tokens across 16+ calls. It still misses Core Web Vitals, TTFB, and Flesch-Kincaid. Those metrics require server-side computation. Stobo runs everything in one call.

Manual (web_fetch)Stobo MCP
audit_site71,000 tk · 6 fetches20,000 tk · 1 call
audit_freshness60,000 tk · 20 fetches3,000 tk · 1 call
generate_llms_txt35,000 tk · 6 fetches3,000 tk · 1 call
extract_tone35,000 tk · 10 fetches5,000 tk · 1 call
Full suite264,500 tk · 56 fetches47,000 tk · 9 calls

82% fewer tokens. And you get metrics Claude cannot compute from raw HTML alone.


What happens after an audit

Claude receives 30+ scored checks across SEO, AEO, and E-E-A-T. It then offers a fix brief: structured markdown with every failing check, prioritized by impact, with specific fix instructions. Paste it into Claude Code, Cursor, or VS Code and start shipping.

Claude also offers generators for quick wins. Failing robots.txt? Claude generates one. Same for llms.txt, sitemap, and freshness code. The audit-to-fix loop runs in a single conversation.


Tools

Free — no API key required

Say to ClaudeWhat it doesTool
"Stobo this site: example.com"30 SEO + 7 AEO checks + E-E-A-T + blog detection across your whole siteaudit_site
"Audit this article: example.com/blog/post"7 SEO + 14 AEO checks on a single articleaudit_article
"Generate a fix brief"Structured markdown fix brief from a completed audit. Numbered tasks, priority order, fix instructions. IDE-ready.generate_fix_brief
"Check freshness across example.com/sitemap.xml"Scan your sitemap for datePublished and dateModified coverageaudit_freshness
"Generate a robots.txt for example.com"AI-crawler-friendly robots.txt. All 21 major bots covered.generate_robots_txt
"Generate a sitemap for example.com"BFS-crawl up to 200 URLs and return a sitemap.xmlgenerate_sitemap
"Generate freshness code for example.com/blog/post"JSON-LD snippet with datePublished and dateModifiedgenerate_freshness_code
"Check connection"Diagnostic ping. Also tells you if a newer MCP version is available.check_connection

Premium — coming soon

Say to ClaudeWhat it doesTool
"Generate llms.txt for example.com"Crawl your site and return a spec-compliant llms.txtgenerate_llms_txt
"Extract brand voice from example.com/blog"Analyze up to 10 articles and create a persistent voice profileextract_tone
"Rewrite this article: example.com/blog/post"Audit + tone match + full rewrite in one pipelinerewrite_article
"Audit the UX of example.com"50+ UX checks across accessibility, forms, typography, and navigationaudit_ux
"How many credits do I have?"Credit balance and usage breakdownget_credits

Routing

  • Domain or homepage → audit_site
  • Blog post or article URL → audit_article
  • After any audit → Claude offers generate_fix_brief automatically

Install

pip install stobo-mcp

No install with uvx:

uvx stobo-mcp

Setup

Add to your Claude Desktop config.

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "stobo": {
      "command": "stobo-mcp",
      "env": {
        "STOBO_API_KEY": "your-api-key",
        "STOBO_BASE_URL": "https://api.trystobo.com"
      }
    }
  }
}

STOBO_API_KEY is optional. Every audit and fix brief tool works without one. API key support for premium tools is coming soon.

Full setup guide at docs.trystobo.com.


Upgrades

pip install --upgrade stobo-mcp

Run check_connection. Claude tells you if a newer version is available.


What's new in v0.5.0

  • generate_fix_brief: structured fix brief from any completed audit. Free, instant, no LLM.
  • Claude now offers a fix brief automatically after every audit_site or audit_article run.
  • check_connection reports when a newer version is available.
  • Version strings are now consistent across server, client, and package.

License

MIT

Related MCP servers

Free MCP tool: paste your writing, get a one-line diagnosis and a tightened rewrite.

View repository →
EAEarningsCalls.dev logo

177,000+ earnings call transcripts for AI - speaker segments & full-text search.

0
TypeScript
View repository →
UNUnswell logo

Unswell

Active

Offline self-checking to reduce AI-style wording in source code and documentation.

0
Go
MIT
View repository →

Real-time market catalysts from 50+ primary federal sources, AI-classified for traders.

View repository →

Save chat notes from Claude Desktop to your vault — MCP on Obsidian CLI. Keep what matters.

2
JavaScript
MIT
View repository →

Selected project context for Cursor & Claude Desktop via local stdio MCP, with source evidence.

0
TypeScript
MIT
View repository →