Skip to content
mcp/skillhub

SEO Audit Console MCP Server

by houtini-aiio.github.houtini-ai/seo-audit-consolev0.12.1

Technical SEO in Claude: GSC + crawl + DataForSEO - audit, market sizing, content recon.

48Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active2d ago

Install SEO Audit Console MCP server

Install in Claude Code

claude mcp add seo-audit-console -e GOOGLE_APPLICATION_CREDENTIALS='<google-application-credentials>' -e DATAFORSEO_PASSWORD='<dataforseo-password>' -e FIRECRAWL_API_KEY='<firecrawl-api-key>' -e SUPADATA_API_KEY='<supadata-api-key>' -e MAJESTIC_API_KEY='<majestic-api-key>' -- npx -y @houtini/seo-audit-console

Configuration

VariableRequiredSecretDescription
GOOGLE_APPLICATION_CREDENTIALSyes—Path to the Google service-account JSON key with Search Console access.
SAC_DATA_DIR——Directory for per-property SQLite databases and reports. Defaults to ~/Documents/seo-audit-console.
DATAFORSEO_USERNAME——DataForSEO API username (optional, enables SERP/keyword/domain/market/recon checks).
DATAFORSEO_PASSWORD—yesDataForSEO API password (optional).
DATAFORSEO_CACHE_DAYS——TTL for the DataForSEO response cache, in days. Default 7.
FIRECRAWL_API_KEY—yesFirecrawl API key (optional). Lets content recon scrape competitor pages. Get one at https://firecrawl.link/2d1PLD8
SUPADATA_API_KEY—yesSupadata API key (optional). Lets content recon transcribe the ranking videos (YouTube/TikTok/X).
MAJESTIC_API_KEY—yesMajestic API key (optional). Enriches link_intersect with Trust Flow + Topical Trust Flow and re-sorts prospects by real authority.
MAJESTIC_CACHE_DAYS——TTL for the Majestic response cache, in days. Default 30.

Freshness

Active — last maintenance signal 2d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-10-06 · 2d ago · GitHub

  2. Latest release

    2026-08-14 · 56d ago · GitHub · v0.5.1

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-10-06 · 2d ago · official registry · v0.12.1

FAQ

›How do I install the SEO Audit Console MCP server in Claude Code?

Run: claude mcp add seo-audit-console -e GOOGLE_APPLICATION_CREDENTIALS='<google-application-credentials>' -e DATAFORSEO_PASSWORD='<dataforseo-password>' -e FIRECRAWL_API_KEY='<firecrawl-api-key>' -e SUPADATA_API_KEY='<supadata-api-key>' -e MAJESTIC_API_KEY='<majestic-api-key>' -- npx -y @houtini/seo-audit-console. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does SEO Audit Console require an API key?

Yes. It expects GOOGLE_APPLICATION_CREDENTIALS, DATAFORSEO_PASSWORD, FIRECRAWL_API_KEY, SUPADATA_API_KEY, MAJESTIC_API_KEY, of which 4 are secrets.

›Can I use SEO Audit Console as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is SEO Audit Console in the official MCP registry?

Yes, as io.github.houtini-ai/seo-audit-console.

Alternatives to SEO Audit Console

Other browser automation MCP servers.

View all