A side-by-side look at the Google Ads MCP by AdPlug and Opus Growth 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 MCP by AdPlug for marketing work over a hosted endpoint; choose Opus Growth for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
adplug_get_status, google_ads_list_accounts, google_ads_account_performance.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 48/100 · Fair | 75/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 1 upvotes |
| Tools | 16 | Not listed |
| Full listing | View Google Ads MCP by AdPlug | View Opus Growth |
adplug_get_statusCheck whether Google Ads is connected and healthy.google_ads_list_accountsList all accessible accounts with names, types, currencies, and MCC hierarchy.google_ads_account_performanceCross-account spend overview in one call (skips MCC managers).google_ads_campaign_performanceCampaign-level metrics, no GAQL required.google_ads_conversion_performanceConversion-action breakdowns with segmentation handled for you.google_ads_daily_trendsDay-by-day metric trends.google_ads_search_termsSearch-term report, sorted by cost.google_ads_shared_set_criteriaContents of shared negative-keyword lists.google_ads_keyword_ideasKeyword research and ideas.google_ads_gaql_docGAQL syntax reference.google_ads_reporting_view_docExact field names, types, and filterability for a reporting view.google_ads_queryRun raw GAQL for custom or advanced queries.No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"google-ads-mcp-by-adplug": {
"url": "https://api.adplug.app/mcp/google-ads"
}
}
}
{
"mcpServers": {
"opus-growth": {
"url": "https://mcp.opus-growth.com/mcp"
}
}
}