A side-by-side look at the Google Ads and Mureo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Ads for marketing work; choose Mureo for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
G
Choose Google Ads when
You need dedicated capabilities in the Marketing domain.
No tool names declared yet. Check the project README from the listing page.
Mureo 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 Ads
No confirmed install command for Google Ads yet — follow the setup steps linked from its listing page rather than a guessed package name.
Google Ads is categorized under Marketing and uses an install path we have not confirmed yet. Mureo belongs to Marketing and uses a local stdio subprocess. Pick Google Ads for marketing work and Mureo 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 Ads has no confirmed install command yet — follow its own setup instructions.
Google Ads has no declared pricing — check the project's own site. Mureo is listed as free. 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-ads-5 and logly-mureo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Ads has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Mureo has 55/100 (Good) with 1 views, 0 installs and 50 GitHub stars.