ActiveCampaign vs Google Ads MCP
A side-by-side look at the ActiveCampaign and Google Ads MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ActiveCampaign for marketing work over a hosted endpoint; choose Google Ads MCP 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 ActiveCampaign when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
ACTIVECAMPAIGN_API_URL, ACTIVECAMPAIGN_API_TOKEN.
Choose Google Ads MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_LOGIN_CUSTOMER_ID, GOOGLE_ADS_REDIRECT_URI, GOOGLE_ADS_PRIVACY_MODE, GOOGLE_ADS_ALLOW_MUTATIONS, GOOGLE_ADS_TOKEN_PATH.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 40/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | ACTIVECAMPAIGN_API_URLACTIVECAMPAIGN_API_TOKEN |
Tools & capabilities
ActiveCampaign tools
No tool names declared yet. Check the project README from the listing page.
Google Ads MCP 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.
ActiveCampaign
{
"mcpServers": {
"activecampaign-2": {
"url": "http://localhost:8765/mcp"
}
}
}
Google Ads MCP
{
"mcpServers": {
"google-ads-mcp": {
"command": "npx",
"args": [
"-y",
"google-ads-mcp-unofficial"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_GOOGLE_ADS_DEVELOPER_TOKEN_HERE",
"GOOGLE_ADS_CLIENT_ID": "YOUR_GOOGLE_ADS_CLIENT_ID_HERE",
"GOOGLE_ADS_CLIENT_SECRET": "YOUR_GOOGLE_ADS_CLIENT_SECRET_HERE",
"GOOGLE_ADS_LOGIN_CUSTOMER_ID": "YOUR_GOOGLE_ADS_LOGIN_CUSTOMER_ID_HERE",
"GOOGLE_ADS_REDIRECT_URI": "YOUR_GOOGLE_ADS_REDIRECT_URI_HERE",
"GOOGLE_ADS_PRIVACY_MODE": "YOUR_GOOGLE_ADS_PRIVACY_MODE_HERE",
"GOOGLE_ADS_ALLOW_MUTATIONS": "YOUR_GOOGLE_ADS_ALLOW_MUTATIONS_HERE",
"GOOGLE_ADS_TOKEN_PATH": "YOUR_GOOGLE_ADS_TOKEN_PATH_HERE"
}
}
}
}
Frequently asked questions
ActiveCampaign is categorized under Marketing and uses a remote HTTP/SSE transport. Google Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick ActiveCampaign for marketing work and Google Ads MCP 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.
ActiveCampaign has no declared pricing — check the project's own site. Google Ads MCP 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 activecampaign-2 and google-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ActiveCampaign has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Google Ads MCP has 41/100 (Fair) with 0 views, 0 installs and 4 GitHub stars.