In-depth architectural comparison of the Google Ad Manager MCP and Opus Growth MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Google Ad Manager MCP
Marketing · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Opus Growth
Marketing · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Google Ad Manager MCP if you need specialized Marketing tools running via a local process. Choose Opus Growth if your workspace requires Marketing integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Google Ad Manager MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: GAM_CREDENTIALS_PATH, GAM_NETWORK_CODES, GAM_MCP_TRANSPORT, GAM_MCP_HOST, GAM_MCP_PORT, GAM_MCP_AUTH_TOKEN.
Google Ad Manager MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Opus Growth belongs to Marketing using remote streaming HTTP/SSE transport. Select Google Ad Manager MCP when you need capabilities focused on marketing and Opus Growth when you require tools for marketing.
Google Ad Manager API integration for managing campaigns, orders, line items, creatives, and advertisers with bulk upload support.
Hosted, OAuth-protected MCP server for advertising operations. One connector covers Google Ads, Meta Ads, Microsoft Advertising, TikTok Ads and LinkedIn Ads, plus Search Console, GA4, YouTube, Tag Manager and Google Business Profile. Every write returns a dry-run preview and is applied only after explicit confirmation.