A side-by-side look at the NotFair GoogleAds and Yandex Metrica MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose NotFair GoogleAds for marketing work as a local process; choose Yandex Metrica for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose NotFair GoogleAds when
You need dedicated capabilities in the Marketing domain.
No tool names declared yet. Check the project README from the listing page.
Yandex Metrica 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 is categorized under Marketing and uses a local stdio subprocess. Yandex Metrica belongs to Marketing and uses a local stdio subprocess. Pick NotFair GoogleAds for marketing work and Yandex Metrica 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.
NotFair GoogleAds has no declared pricing — check the project's own site. Yandex Metrica 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 yandex-metrica 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 51/100 (Good) with 1 views, 0 installs and 3,959 GitHub stars. Yandex Metrica has 45/100 (Fair) with 2 views, 0 installs and 4 GitHub stars.