Google ads mcp
The Cowork Agent for Everything — trainable advertising AI + 14 platform MCP servers + agent skills. Based on minimind (42k stars). Train from zero in 2 hours.
npx -y skills add itallstartedwithaidea/MiniAgent --skill google-ads-mcpAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the user needs to SET UP, CONFIGURE, or TROUBLESHOOT MCP server connections for Google Ads or any advertising platform. Trigger for: MCP setup, MCP config, API credentials, OAuth, developer token, authentication errors, connection issues, 'connect to Google Ads', 'set up MCP', or any MCP server configuration question.
SKILL.md
1.8 KB, as published. Nobody here has run it
Google Ads MCP Setup Skill
Guide for connecting MiniAgent's MCP servers to real ad platform APIs.
Claude Code Setup
claude mcp add miniagent-google -- python -m miniagent.mcp.google_ads
Or add to .mcp.json:
{
"mcpServers": {
"miniagent-google": {
"command": "python",
"args": ["-m", "miniagent.mcp.google_ads"],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "your-token",
"GOOGLE_ADS_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
"GOOGLE_ADS_CLIENT_SECRET": "your-secret",
"GOOGLE_ADS_REFRESH_TOKEN": "your-refresh-token",
"GOOGLE_ADS_CUSTOMER_ID": "1234567890"
}
}
}
}
Getting Credentials
- Developer Token: Google Ads → Tools → API Center → Apply
- OAuth Client: Google Cloud Console → APIs → Credentials → Create OAuth Client ID
- Refresh Token: Run
python -m miniagent.mcp.google_ads --oauthto start the OAuth flow - Customer ID: The 10-digit number in the top-right of Google Ads (no dashes)
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
AUTHENTICATION_ERROR | Bad credentials | Check all 4 env vars are set |
AUTHORIZATION_ERROR | No access to account | Verify customer_id, check MCC access |
DEVELOPER_TOKEN_NOT_APPROVED | Token pending | Apply at Google Ads API Center |
RATE_LIMIT_EXCEEDED | Too many requests | Add retry logic, check quota |
Gives 0 of the 12 instructions most project setup skills give
Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-06
- ask one question at a timein 29 of 999, across 28 files
- detect the package manager from lockfilesin 28 of 999, across 9 files
- present findings to the userin 25 of 999, across 4 files
- explore current repo statein 24 of 999, across 3 files
- update the agent skills block in place if it existsin 24 of 999, across 3 files
- install husky lint-staged and prettierin 23 of 999, across 4 files
- create the lintstagedrc filein 22 of 999, across 3 files
- commit all changed filesin 22 of 999, across 3 files
- run lint-staged to verify it worksin 22 of 999, across 3 files
- initialize huskyin 21 of 999, across 2 files
- create the husky pre-commit filein 21 of 999, across 2 files
- create a prettierrc file if missingin 21 of 999, across 2 files
Said here and by no other author read
- add the server via claude mcp add command
- obtain a developer token from google ads
- create an oauth client id in google cloud console
- run the oauth flow script to get a refresh token
- verify the customer id has no dashes
- check environment variables for authentication errors
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.