mcp-google-ads
Allows querying and analyzing Google Ads accounts, including campaign performance, keywords, search terms, and account analytics, with support for multiple accounts and OAuth/service account authentication.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-google-adsShow me campaign performance for account my-client last month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-google-ads
Multi-account Google Ads MCP server. Connect any number of Google Ads accounts to Claude, Cursor, Codex, or any MCP-compatible AI assistant — query campaign performance, keywords, search terms, and account analytics by name in the same session.
# Install: uvx mcp-google-ads-multi
# Ask your AI:
"Show me campaign performance for account my-client last month"
"What search terms drove conversions for client-acme in Q2?"
"Compare my-account's spend between January and February"
"Which keywords have quality scores below 5 for campaign 123?"Start Here
You are | Start with | Time |
Installing the server | 10 min | |
Connecting several accounts | 10 min | |
Extending tools | docs/architecture.md and | 15 min |
Related MCP server: Google Ads MCP Server
Architecture
flowchart TD
Client[MCP client] -->|stdio or SSE| Server[gads/server.py]
subgraph Local config
Env[environment] --> Accounts[accounts.json]
Accounts --> Auth[OAuth or service account]
end
Server --> AccountsMod[gads/accounts.py]
Server --> Query[gads/query.py]
Server --> Retry[gads/retry.py]
AccountsMod --> Auth
Query -->|GAQL| Ads[Google Ads API]
Retry -->|backoff| Ads
Ads -->|metrics| Server
Server -->|tool result| ClientMore detail lives in docs/architecture.md.
Primary Workflow
flowchart TD
Ask([User asks for Ads data]) --> Tool[Select MCP tool]
Tool --> Account{Account named?}
Account -->|yes| LoadNamed[Load named account]
Account -->|no| LoadDefault[Load default account]
LoadNamed --> Auth[Resolve credentials]
LoadDefault --> Auth
Auth --> Query[Build GAQL query]
Query --> Execute[Call Google Ads API]
Execute --> Retry{Rate limited?}
Retry -->|yes| Backoff[Retry with backoff]
Retry -->|no| Return[Return metrics]
Backoff --> ExecuteWhy this one?
Most Google Ads MCP servers support one account per server process. This one lets you configure multiple accounts and switch between them per tool call — no restart needed.
Feature | This server | Others |
Multiple accounts | Yes — named, switchable | No — one per process |
OAuth + service account | Both, mixed per account | Usually one type |
Quality score data | Yes | Rarely |
Search terms report | Yes | Sometimes |
Rate limit retry | Yes — exponential backoff | No |
SSE transport (remote) | Yes | Varies |
Quickstart
1. Get a developer token — apply at Google Ads API Center (free, ~3 business days)
2. Create OAuth credentials — Google Cloud Console → Enable Google Ads API → Credentials → OAuth client ID → Desktop app
3. Create your accounts config:
mkdir -p ~/.config/mcp-google-ads
cp accounts.example.json ~/.config/mcp-google-ads/accounts.json
# Edit it — add your accounts4. Add to your MCP client config:
{
"mcpServers": {
"google-ads": {
"command": "uvx",
"args": ["mcp-google-ads-multi"],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "your-developer-token",
"GOOGLE_ADS_ACCOUNTS_CONFIG": "/Users/you/.config/mcp-google-ads/accounts.json"
}
}
}
}5. Restart your AI client. Done.
Accounts config
{
"default": "my-account",
"accounts": {
"my-account": {
"type": "oauth",
"client_id": "YOUR_CLIENT_ID.apps.googleusercontent.com",
"client_secret": "YOUR_CLIENT_SECRET",
"token_file": "~/.config/mcp-google-ads/my-account.token"
},
"client-acme": {
"type": "oauth",
"client_id": "YOUR_CLIENT_ID.apps.googleusercontent.com",
"client_secret": "YOUR_CLIENT_SECRET",
"token_file": "~/.config/mcp-google-ads/client-acme.token"
}
}
}Set GOOGLE_ADS_DEVELOPER_TOKEN in your environment. All other credentials stay local.
Available tools
Tool | What it does |
| Show all configured accounts |
| Change the default account |
| List all accessible Google Ads accounts under your login |
| Total clicks, cost, conversions for a period |
| All campaigns with status, budget, 30-day metrics |
| Campaign metrics for any date range |
| Two date ranges side-by-side with deltas |
| Keyword metrics + quality scores |
| Actual search queries that triggered your ads |
| Ad-level CTR and conversions |
Environment variables
Variable | Default | Description |
| required | Your Google Ads API developer token |
|
| Path to accounts config |
|
| Set to |
|
| SSE bind host |
|
| SSE bind port |
License
MIT
Reference
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/apexradius/mcp-google-ads'
If you have feedback or need assistance with the MCP directory API, please join our Discord server