Server facts
search-console-mcp
Project
- Author
- saurabhsharma2u
- License
- MIT
- Category
- Search & Web Data
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 304
- Last commit
- Data as of
Tags
- Google Search
- Google Search Console
- google webmaster
Overview
Traffic investigations in search-console-mcp can combine analytics_query breakdowns by query, page, country, and device with analytics_compare for period comparisons and drop attribution. analytics_anomalies checks Google and Bing for unusual traffic, while compare_engines puts their search performance side by side. Keyword analysis through seo_audit covers competing pages, lost queries, weak click-through rates, and striking-distance opportunities. GA4 tools add engagement, conversions, e-commerce, realtime metrics, and user behavior to the available reporting.
Property and sitemap management sit alongside URL inspection, PageSpeed checks, and structured-data validation. Agents can submit URLs through Google's indexing API, Bing submission, or IndexNow, then check Google's notification status or Bing's remaining submission quota. Multi-account support selects credentials for the requested site, while diagnostics tests connectivity when authentication or empty results need investigation. For orientation, get_started supplies a map of capabilities, active platforms, and suggested workflows. The server runs on Node.js, communicates over stdio, and is MIT-licensed.
search-console-mcp setup notes
- search-console-mcp records stdio only; confirm a network transport upstream before planning remote access.