Octoboost
Batch-audit landing pages and marketing URLs for SEO and generative-engine visibility before you push distribution.
Overview
OctoBoost is a MCP server for the Launch phase that analyzes multiple URLs with categorized SEO and GEO checks and scored results via the OctoBoost API.
What is this MCP server?
- Analyze multiple URLs in one agent session via stdio MCP (npm octoboost-mcp-server v1.0.6).
- Returns categorized SEO and GEO checks with scored results per URL.
- Authenticates to OctoBoost’s SEO API with OCTOBOOST_API_KEY (required secret).
- stdio transport fits Claude Code, Cursor, and other MCP hosts without a custom plugin.
- Useful for prioritizing on-page fixes across a site map or competitor URLs before launch content ships.
- Published server version 1.0.6
- npm identifier octoboost-mcp-server with stdio transport
- One required secret env var: OCTOBOOST_API_KEY
What problem does it solve?
You have several live or draft URLs and no fast way to see which SEO and AI-search readiness issues matter most across all of them.
Who is it for?
Indie builders running pre-launch or post-ship audits on multiple marketing URLs with Claude Code or Cursor and an OctoBoost API key.
Skip if: Teams that only need a single-page Lighthouse run inside CI with no GEO categorization or agent-driven batch workflow.
What do I get? / Deliverables
Your agent returns categorized, scored SEO/GEO findings per URL so you can queue concrete fixes before launch and growth work.
- Categorized SEO and GEO check results per analyzed URL
- Scored audit summaries suitable for a fix backlog
- Agent-readable batch output across multiple URLs
Recommended MCP Servers
Journey fit
OctoBoost scores live URLs against SEO and GEO check categories, which maps to the Launch phase where solo builders fix discoverability and AI-search signals. GEO is the canonical shelf because the server explicitly pairs SEO with GEO-style checks and scored results aimed at AI-search and search visibility, not app-store listing work.
How it compares
MCP bridge to a hosted SEO scoring API, not an on-repo agent skill that edits HTML for you.
Common Questions / FAQ
Who is io.github.eugenregehr/octoboost for?
Solo builders and small teams who want their AI coding agent to batch-analyze URLs for SEO and GEO signals using OctoBoost rather than manual checklist tools.
When should I use io.github.eugenregehr/octoboost?
Use it during Launch when you are validating marketing pages, docs, or landing URLs for search and generative-engine visibility before or right after you start distribution.
How do I add io.github.eugenregehr/octoboost to my agent?
Install the npm package octoboost-mcp-server, add a stdio MCP entry in your host config, and set the required secret OCTOBOOST_API_KEY for OctoBoost API authentication.