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.

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

Related MCP server: DevHelm MCP Server

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

Premium — coming soon

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