Gadschain vs Google Ads
A side-by-side look at the Gadschain and Google Ads MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gadschain for marketing work; choose Google Ads 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 Gadschain when
- You need dedicated capabilities in the Marketing domain.
- Its auth model fits you: OAuth 2.0.
- 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, GOOGLE_ADS_CUSTOMER_ID, GOOGLE_ADS_API_VERSION, LOG_LEVEL.
Choose Google Ads 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_REFRESH_TOKEN, GOOGLE_ADS_CUSTOMER_ID, GOOGLE_ADS_LOGIN_CUSTOMER_ID. - You want tools like
gads_run_gaql, gads_list_accounts, gads_account_info.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 33/100 · Emerging | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GOOGLE_ADS_DEVELOPER_TOKENGOOGLE_ADS_CLIENT_IDGOOGLE_ADS_CLIENT_SECRETGOOGLE_ADS_REFRESH_TOKENGOOGLE_ADS_LOGIN_CUSTOMER_IDGOOGLE_ADS_CUSTOMER_IDGOOGLE_ADS_API_VERSIONLOG_LEVEL | GOOGLE_ADS_DEVELOPER_TOKENGOOGLE_ADS_CLIENT_IDGOOGLE_ADS_CLIENT_SECRETGOOGLE_ADS_REFRESH_TOKENGOOGLE_ADS_CUSTOMER_IDGOOGLE_ADS_LOGIN_CUSTOMER_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 22 |
| Full listing | View Gadschain | View Google Ads |
Tools & capabilities
Gadschain tools
No tool names declared yet. Check the project README from the listing page.
Google Ads tools 22
gads_run_gaqlRun any raw GAQL query — escape hatch for custom reportsgads_list_accountsList all accessible Google Ads accountsgads_account_infoName, currency, timezone, manager flag, statusgads_list_campaignsCampaigns with status, channel type, bidding strategygads_campaign_performanceImpressions, clicks, CTR, CPC, cost, conversions, CPA, ROASgads_ad_group_performanceAd group metrics with campaign contextgads_keyword_performanceKeywords with match type, quality score, cost, conversionsgads_search_terms_reportActual user queries that triggered ads — find negatives and opportunitiesgads_conversions_by_campaignConversions × conversion action per campaigngads_list_conversion_actionsAll conversion actions with category, type, counting methodgads_list_rsasRSAs with all headlines, descriptions, Ad Strength, approval statusgads_rsa_asset_performancePer-asset performance labels: BEST / GOOD / LOW / PENDING / LEARNING- +10 more on 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.
Gadschain
No confirmed install command for Gadschain yet — follow the setup steps linked from its listing page rather than a guessed package name.
Google Ads
{
"mcpServers": {
"google-ads-4": {
"command": "npx",
"args": [
"-y",
"google-ads-mcp"
],
"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_REFRESH_TOKEN": "YOUR_GOOGLE_ADS_REFRESH_TOKEN_HERE",
"GOOGLE_ADS_CUSTOMER_ID": "YOUR_GOOGLE_ADS_CUSTOMER_ID_HERE",
"GOOGLE_ADS_LOGIN_CUSTOMER_ID": "YOUR_GOOGLE_ADS_LOGIN_CUSTOMER_ID_HERE"
}
}
}
}
Frequently asked questions
Gadschain is categorized under Marketing and uses an install path we have not confirmed yet. Google Ads belongs to Marketing and uses a local stdio subprocess. Pick Gadschain for marketing work and Google Ads 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. Gadschain has no confirmed install command yet — follow its own setup instructions.
Gadschain has no declared pricing — check the project's own site. Auth: oauth 2.0. Google Ads 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 gadschain and google-ads-4 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gadschain has a quality signal of 33/100 (Emerging) with 4 views, 0 installs and 0 GitHub stars. Google Ads has 52/100 (Good) with 1 views, 0 installs and 1 GitHub stars.