A side-by-side look at the Mureo 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 Mureo for marketing work as a local process; choose NotFair GoogleAds 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 Mureo 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.
Mureo is categorized under Marketing and uses a local stdio subprocess. NotFair GoogleAds belongs to Marketing and uses a local stdio subprocess. Pick Mureo 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.
Mureo is listed as free. Auth: oauth 2.0. NotFair GoogleAds 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 logly-mureo and notfair-googleads as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mureo has a quality signal of 55/100 (Good) with 1 views, 0 installs and 51 GitHub stars. NotFair GoogleAds has 51/100 (Good) with 1 views, 0 installs and 3,959 GitHub stars.