Search Console MCP vs Seo Audit
A side-by-side look at the Search Console MCP and Seo Audit MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Search Console MCP for marketing work as a local process; choose Seo Audit for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Search Console MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
get_started, sites_list, sites_manage.
Choose Seo Audit when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
ai_search_diagnostic, full_seo_audit, email_seo_report.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 71/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 308 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 25 | 5 |
| Full listing | View Search Console MCP | View Seo Audit |
Tools & capabilities
Search Console MCP tools 25
get_startedStart here. Returns a complete map of this server's capabilities, active platforms, and recommended workflows. Call this once at the beginning of any session.sites_listList verified web properties across Google Search Console, Bing Webmaster Tools, or GA4.sites_manageAdd or delete a web property from Google Search Console or Bing Webmaster Tools.accounts_manageManage Google Search Console service accounts and site permissions.sitemaps_listList submitted XML sitemaps and status for a site.sitemaps_submitSubmit a new XML sitemap to Google Search Console and/or Bing Webmaster Tools.sitemaps_deleteDelete a sitemap from Google Search Console or Bing Webmaster Tools.analytics_queryUnified search performance query replacing single-dimension tools. Supports queries, pages, countries, devices, and search appearances.analytics_comparePeriod-over-period search performance comparisons, trends, and traffic drop attributions.analytics_anomaliesDetect search traffic anomalies across Google and Bing.analytics_advancedGoogle Analytics 4 (GA4) e-commerce, realtime metrics, user behavior, and conversion funnels.genai_query_insightsDetect likely generative-AI / AI-Mode / conversational fanout queries across Google and Bing. Because neither search engine exposes generative-AI citation data via its public API yet, this matches heuristic patterns (prompt verbs, follow-ups, conversational phrasing) on regular query-level performance data; it is an undercount, not an official report.- +13 more on the listing page
Seo Audit tools 5
ai_search_diagnosticAudit ANY URL for AI-search readiness only (AEO/GEO/LLMO) — how likely ChatGPT, Claude, Perplexity & Google AI are to cite it. Checks ~7 AI-citation signals (FAQ/structured-data/entity schema, citable stats, llms.txt, author/E-E-A-T, OG). Returns a weighted 0–100 AI-readiness score + top fixes. Takes a `url`. Use full_seo_audit for the broader SEO picture, or get_my_store_audit for the user's own connected store. Returns a summary of the top issues; the complete written report is available via email_seo_report.full_seo_auditCrawl-audit ANY URL across the WHOLE SEO surface (no login needed): the AI-search signals PLUS on-page SEO (title/meta/headings/content), technical SEO (HTTPS, robots.txt, XML sitemap, canonical, mobile), and — for Shopify stores — product/offer/review/breadcrumb schema and image-alt coverage. Returns a weighted 0–100 score + top issues. Takes a `url`. This audits an arbitrary website by crawling it — for the user's OWN connected store with real analytics, use get_my_store_audit. Returns a summary of the top issues; the complete written report is available via email_seo_report.email_seo_reportALWAYS OFFER THIS after running an audit: the audit tools return a summary of the top issues, while this sends the complete written report — every check, its evidence, and the fix in priority order. Ask the user which email address to send it to; never guess or reuse an address they did not give in this conversation. Email the full written SEO/AEO report for an audit this session already ran. Takes the audit_id returned by ai_search_diagnostic or full_seo_audit, plus the user's email. ONLY use an email address the user explicitly gave you - never guess or invent one. Offer this after presenting audit results.subscribe_to_seoaixStart an SeoAiX subscription — autopilot SEO/AEO for Shopify stores (reads GSC/GA4/Merchant Center, plans a month of content, writes and publishes articles with schema, fixes meta/alt-text, and attributes revenue to content). Plans from $19/mo with a free trial. Returns a personalised signup link; payment and store connection complete in the browser. Optionally pass the user's `email` and `store_url` (ONLY if the user explicitly provided them - never invent either) so the team can follow up.get_my_store_auditGet the user's OWN connected Shopify store audit — the deep 12-category report SeoAiX runs INSIDE the app using the store's real catalog, performance and analytics (technical, performance, on-page, schema, AEO, analytics, e-commerce, etc.) — far beyond what crawling a URL can see. Takes no url. Needs an SeoAiX API key (free at seoaix.com → Settings) + a connected store: pass the key either as `Authorization: Bearer inxy_sk_…` or as the `api_key` argument.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Search Console MCP
{
"mcpServers": {
"saurabhsharma2u-search-console-mcp": {
"command": "npx",
"args": [
"-y",
"search-console-mcp"
]
}
}
}
Seo Audit
{
"mcpServers": {
"seo-audit": {
"url": "https://inxy.ai/api/mcp"
}
}
}
Frequently asked questions
Search Console MCP is categorized under Marketing and uses a local stdio subprocess. Seo Audit belongs to Marketing and uses a remote HTTP/SSE transport. Pick Search Console MCP for marketing work and Seo Audit for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Search Console MCP is listed as free. Auth: oauth 2.0. Seo Audit has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add saurabhsharma2u-search-console-mcp and seo-audit as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Search Console MCP has a quality signal of 71/100 (Great) with 4 views, 0 installs and 308 GitHub stars. Seo Audit has 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars.