A side-by-side look at the Ads MCP and Maqui Analytics MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ads MCP for marketing work as a local process; choose Maqui Analytics 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 MCP when
You need dedicated capabilities in the Marketing domain.
No tool names declared yet. Check the project README from the listing page.
Maqui Analytics 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 MCP is categorized under Marketing and uses a local stdio subprocess. Maqui Analytics belongs to Marketing and uses a remote HTTP/SSE transport. Pick Ads MCP for marketing work and Maqui Analytics 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 MCP has no declared pricing — check the project's own site. Maqui Analytics 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 ads-mcp-3 and maqui-analytics as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ads MCP has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Maqui Analytics has 66/100 (Great) with 4 views, 0 installs and 0 GitHub stars.