NotFair GoogleAds vs SearchConsole.ai

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

NotFair GoogleAds logoNotFair GoogleAdsMarketing · Remote HTTP/SSEHosted Google Ads MCP with OAuth, 117 tools, MCC routing, image assets, and approval-gated writes.49FairAuth: oauth 2.0
S
SearchConsole.aiMarketing
Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.37FairAuth: not declared

Verdict: choose NotFair GoogleAds for marketing work over a hosted endpoint; choose SearchConsole.ai for marketing. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

NotFair GoogleAds logoChoose NotFair GoogleAds when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore NotFair GoogleAds

S
Choose SearchConsole.ai when

  • You need dedicated capabilities in the Marketing domain.
Explore SearchConsole.ai

Feature & specification comparison

Rows where the two servers differ are marked.

SpecNotFair GoogleAds logoNotFair GoogleAds
S
SearchConsole.ai
CategoryMarketingMarketing
Quality signal49/100 · Fair37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthOAuth 2.0Not declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars4,046—
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

NotFair GoogleAds tools

No tool names declared yet. Check the project README from the listing page.

SearchConsole.ai tools

No tool names declared yet. Check the project README from 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.

NotFair GoogleAds

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "notfair-googleads": {
      "url": "https://notfair.co/api/mcp/notfair"
    }
  }
}

SearchConsole.ai

No confirmed install command for SearchConsole.ai yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

NotFair GoogleAds is categorized under Marketing and uses a remote HTTP/SSE transport. SearchConsole.ai belongs to Marketing and uses an install path we have not confirmed yet. Pick NotFair GoogleAds for marketing work and SearchConsole.ai 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. SearchConsole.ai has no confirmed install command yet — follow its own setup instructions.

NotFair GoogleAds has no declared pricing — check the project's own site. Auth: oauth 2.0. SearchConsole.ai 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 notfair-googleads and searchconsole-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, NotFair GoogleAds has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 4,046 GitHub stars. SearchConsole.ai has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.