Vibeads MCP vs Search Console MCP

A side-by-side look at the Vibeads MCP and Search Console MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Vibeads MCP logoVibeads MCPMarketing · Local subprocess (stdio)Manage Google Ads from Claude: read metrics, draft campaigns, publish with human approval.57GoodAuth: not declaredSearch Console MCP logoSearch Console MCPMarketing · Local subprocess (stdio)An MCP server to interact with Google Search Console and Bing Webmasters.71GreatAuth: oauth 2.0

Verdict: choose Vibeads MCP for marketing work as a local process; choose Search Console MCP for marketing as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Vibeads MCP logoChoose Vibeads MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: VIBEADS_API_KEY.
  • You want tools like list_campaigns, get_campaign_details, get_account_health_score.
Explore Vibeads MCP

Search Console MCP logoChoose 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.
Explore Search Console MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecVibeads MCP logoVibeads MCPSearch Console MCP logoSearch Console MCP
CategoryMarketingMarketing
Quality signal57/100 · Good71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredFree
Required env varsVIBEADS_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1306
Directory activity 2 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools2925

Tools & capabilities

Vibeads MCP tools 29

  • list_campaignsYour campaigns in VibeAds (published, imported and drafts) with status, budget and category. Campaigns only in your Google Ads account are listed by `find_campaigns_to_import
  • get_campaign_detailsDeep dive on one campaign: metrics, ad groups, targeting, landing pages, diagnostics
  • get_account_health_score0-100 score + letter grade across 6 dimensions, optionally per-campaign
  • get_search_term_analysisWasted spend + winners from each campaign's latest synced search terms, which cover the 7 days before that sync (configurable cost threshold)
  • get_diagnosticsLatest agent-optimize diagnostics with severity + recommended fix (up to 50)
  • find_campaigns_to_importBefore importing: the campaigns in your Google Ads account, read from Google Ads, each marked with whether it is in VibeAds (VibeAds manages only the campaigns in it). Called `list_google_ads_campaigns` in 0.2.15
  • get_performance_reportOne campaign's or a whole account's figures for a period you choose (a preset or two dates, up to 90 days), read live from Google Ads, optionally by day, device, hour, ad group, keyword or location. Money in the account's currency. VibeAds builds every query; the assistant only picks the period and…
  • audit_google_ads_accountAn audit of one connected Google Ads account, read live from Google Ads: up to 25 Search campaigns over the last 30 days, whether or not they are in VibeAds, with a 0-100 health score and grade for the account and each campaign, the issues grouped by check with what fixes each in Google Ads, and ea…
  • list_keywordsOne published campaign's ad groups, keywords and negative keywords, read live from Google Ads: match type, status, max CPC and 30 days of clicks, cost and conversions
  • research_keywordsKeyword ideas from Google's Keyword Planner for seed keywords, a web page or both, in the places you name: average monthly searches, competition and top-of-page bid range. Pro/Max, 2 credits (a repeat within 90 days is free)
  • list_google_ads_accountsEvery connected Google Ads account, switched on or not, with the manager account (MCC) each client account sits under
  • list_google_recommendationsGoogle's own recommendations for an account (its Recommendations page), with Google's estimate and whether each can be applied from the chat
  • +17 more on the listing page

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

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.

Vibeads MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-335": {
      "command": "npx",
      "args": [
        "-y",
        "@vibeads/mcp"
      ],
      "env": {
        "VIBEADS_API_KEY": "YOUR_VIBEADS_API_KEY_HERE"
      }
    }
  }
}

Search Console MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "saurabhsharma2u-search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "search-console-mcp"
      ]
    }
  }
}

Frequently asked questions

Vibeads MCP is categorized under Marketing and uses a local stdio subprocess. Search Console MCP belongs to Marketing and uses a local stdio subprocess. Pick Vibeads MCP for marketing work and Search Console MCP 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.

Vibeads MCP has no declared pricing — check the project's own site. Search Console MCP is listed as free. Auth: oauth 2.0. 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 mcp-335 and saurabhsharma2u-search-console-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Vibeads MCP has a quality signal of 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Search Console MCP has 71/100 (Great) with 4 views, 0 installs and 306 GitHub stars.