Google Adwords vs NotFair GoogleAds

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

Google Adwords logoGoogle AdwordsMarketingMCP server for Google Ads campaign and budget management32EmergingAuth: not declaredNotFair 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

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

Which MCP server should you choose?

Google Adwords logoChoose Google Adwords when

  • You need dedicated capabilities in the Marketing domain.
Explore Google Adwords

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGoogle Adwords logoGoogle AdwordsNotFair GoogleAds logoNotFair GoogleAds
CategoryMarketingMarketing
Quality signal32/100 · Emerging49/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars04,055
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Google Adwords tools

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

NotFair GoogleAds 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.

Google Adwords

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

NotFair GoogleAds

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

Frequently asked questions

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

Google Adwords has no declared pricing — check the project's own site. NotFair GoogleAds has no declared pricing — check the project's own site. 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 google-adwords and notfair-googleads as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Google Adwords has a quality signal of 32/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. NotFair GoogleAds has 49/100 (Fair) with 1 views, 0 installs and 4,055 GitHub stars.