Google Ads vs Openai Ads MCP
A side-by-side look at the Google Ads and Openai 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 Google Ads for marketing work; choose Openai 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 Google Ads when
- You need dedicated capabilities in the Marketing domain.
- You have the keys it needs:
GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_REFRESH_TOKEN, GOOGLE_ADS_LOGIN_CUSTOMER_ID. - You want tools like
google_ads_list_accounts, google_ads_get_account_details, google_ads_run_gaql.
Choose Openai Ads MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_ADS_API_KEY. - You want tools like
get_ad_account, list_campaigns, get_campaign.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 45/100 · Fair | 56/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | GOOGLE_ADS_DEVELOPER_TOKENGOOGLE_ADS_CLIENT_IDGOOGLE_ADS_CLIENT_SECRETGOOGLE_ADS_REFRESH_TOKENGOOGLE_ADS_LOGIN_CUSTOMER_ID | OPENAI_ADS_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 45 | 11 |
| Full listing | View Google Ads | View Openai Ads MCP |
Tools & capabilities
Google Ads tools 45
google_ads_list_accountsList Google Ads customer accounts accessible with the current credentials.google_ads_get_account_detailsGet detailed information for a specific Google Ads customer account.google_ads_run_gaqlExecute a raw GAQL (Google Ads Query Language) query.google_ads_get_insightsQuery Google Ads performance insights with intelligent query planning.google_ads_get_campaignsList campaigns for a Google Ads account with status, budget, channel type, and bidding strategy.google_ads_get_adgroupsList ad groups for a Google Ads account, optionally filtered by campaign.google_ads_get_keyword_performanceGet keyword-level performance data from keyword_view resource.google_ads_validate_queryValidate metric/dimension/resource compatibility BEFORE executing a query.google_ads_health_checkRead-only connectivity check.google_ads_get_account_hierarchyList accessible customers and, where possible, manager/client relationships from GAQL customer_client.google_ads_get_conversion_actionsList conversion actions with status, type, category, primary/include-in-conversions flags, owner customer, and last activity dates when supported.google_ads_get_change_eventsFetch recent change_event rows.- +33 more on the listing page
Openai Ads MCP tools 11
get_ad_accountFetch the ad account for the configured key. Great as a connectivity check.list_campaignsList campaigns (objective, budget, country targeting).get_campaignFetch a single campaign by ID.list_ad_groupsList ad groups, optionally filtered by campaign.get_ad_groupFetch a single ad group by ID (bidding config, context hints).list_adsList ads, optionally filtered by ad group.get_adFetch a single ad by ID (creative + review status).get_account_insightsPerformance insights for the whole account.get_campaign_insightsPerformance insights for one campaign.get_ad_group_insightsPerformance insights for one ad group.get_ad_insightsPerformance insights for one ad.
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.
Openai Ads MCP
{
"mcpServers": {
"openai-ads-mcp": {
"command": "npx",
"args": [
"-y",
"@hypd-ai/openai-ads-mcp"
],
"env": {
"OPENAI_ADS_API_KEY": "YOUR_OPENAI_ADS_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Google Ads is categorized under Marketing and uses an install path we have not confirmed yet. Openai Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick Google Ads for marketing work and Openai 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. 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. Openai Ads MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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-10 and openai-ads-mcp 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 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Openai Ads MCP has 56/100 (Good) with 4 views, 0 installs and 5 GitHub stars.
