A side-by-side look at the Ads and NotFair GoogleAds MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ads for marketing work over a hosted endpoint; 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?
Choose Ads when
You need dedicated capabilities in the Marketing domain.
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.
Ads is categorized under Marketing and uses a remote HTTP/SSE transport. NotFair GoogleAds belongs to Marketing and uses a remote HTTP/SSE transport. Pick Ads 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.
Ads 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 ads-2 and notfair-googleads as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ads has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. NotFair GoogleAds has 49/100 (Fair) with 1 views, 0 installs and 3,970 GitHub stars.