mcp-google-ads
Multi-account Google Ads MCP server that allows connecting any number of Google Ads accounts and querying campaign performance, keywords, search terms, and account analytics by name in the same session.
README
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?"
Why 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 accounts
4. 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 |
|---|---|
list_accounts |
Show all configured accounts |
set_default_account |
Change the default account |
list_customers |
List all accessible Google Ads accounts under your login |
get_account_summary |
Total clicks, cost, conversions for a period |
list_campaigns |
All campaigns with status, budget, 30-day metrics |
get_campaign_performance |
Campaign metrics for any date range |
compare_periods |
Two date ranges side-by-side with deltas |
get_keyword_performance |
Keyword metrics + quality scores |
search_terms_report |
Actual search queries that triggered your ads |
get_ad_performance |
Ad-level CTR and conversions |
Environment variables
| Variable | Default | Description |
|---|---|---|
GOOGLE_ADS_DEVELOPER_TOKEN |
required | Your Google Ads API developer token |
GOOGLE_ADS_ACCOUNTS_CONFIG |
~/.config/mcp-google-ads/accounts.json |
Path to accounts config |
MCP_TRANSPORT |
stdio |
Set to sse for remote deployment |
MCP_HOST |
127.0.0.1 |
SSE bind host |
MCP_PORT |
3001 |
SSE bind port |
License
MIT
<!-- mcp-name: io.github.Ayo-Fam/mcp-google-ads -->
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.