Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @zleventer/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
GOOGLE_ADS_DEVELOPER_TOKEN=<secret> GOOGLE_ADS_CLIENT_ID=<secret> GOOGLE_ADS_CLIENT_SECRET=<secret> GOOGLE_ADS_REFRESH_TOKEN=<secret> GOOGLE_ADS_CUSTOMER_ID=<value> GOOGLE_ADS_LOGIN_CUSTOMER_ID=<value> claude mcp add io.github.zleventer-google-ads-mcp -- npx -y @zleventer/google-ads-mcp@1.0.1Execute em um terminal.
{ "mcpServers": { "io.github.zleventer-google-ads-mcp": { "command": "npx", "args": [ "-y", "@zleventer/[email protected]" ], "env": { "GOOGLE_ADS_DEVELOPER_TOKEN": "<secret>", "GOOGLE_ADS_CLIENT_ID": "<secret>", "GOOGLE_ADS_CLIENT_SECRET": "<secret>", "GOOGLE_ADS_REFRESH_TOKEN": "<secret>", "GOOGLE_ADS_CUSTOMER_ID": "<value>", "GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<value>" } } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirMCP server for Google Ads — diagnose spend efficiency, impression share, and asset performance from Claude.
22 tools across campaigns, keywords, RSAs, assets, audiences, geo/device splits, impression share, auction insights, and budget pacing — plus a raw GAQL escape hatch. Built for B2B paid search teams and agencies running real diagnosis, not just dashboard-style "list my campaigns" queries.
Most Google Ads MCP servers stop at "list campaigns + basic metrics." This one goes after the questions paid search teams actually ask: which RSA assets are labeled LOW so I can replace them, which keywords burn budget with zero conversions, who am I losing impression share to in auction insights, what's my mobile vs. desktop CPA gap, which campaigns are budget-limited right now. Those are the levers you pull to fix performance — and they're all first-class tools here.
Differentiated from the official googleads/google-ads-mcp: ships RSA asset performance labels, auction insights, impression share analysis, geo/device splits, audience targeting inspection, and budget pacing.
Once installed, ask Claude things like:
🎥 Walkthrough video coming soon — diagnosing wasted spend from Claude in under 60 seconds.
https://www.googleapis.com/auth/adwords scopeclaude_desktop_config.json){
"mcpServers": {
"google-ads": {
"command": "npx",
"args": ["-y", "google-ads-mcp"],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_TOKEN",
"GOOGLE_ADS_CLIENT_ID": "YOUR_CLIENT_ID",
"GOOGLE_ADS_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
"GOOGLE_ADS_REFRESH_TOKEN": "YOUR_REFRESH_TOKEN",
"GOOGLE_ADS_CUSTOMER_ID": "1234567890"
}
}
}
}
{
"mcpServers": {
"google-ads": {
"command": "node",
"args": ["/path/to/google-ads-mcp/dist/index.js"],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_TOKEN",
"GOOGLE_ADS_CLIENT_ID": "YOUR_CLIENT_ID",
"GOOGLE_ADS_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
"GOOGLE_ADS_REFRESH_TOKEN": "YOUR_REFRESH_TOKEN",
"GOOGLE_ADS_CUSTOMER_ID": "1234567890"
}
}
}
}
~/.cursor/mcp.json){
"mcpServers": {
"google-ads": {
"command": "npx",
"args": ["-y", "google-ads-mcp"],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_TOKEN",
"GOOGLE_ADS_CLIENT_ID": "YOUR_CLIENT_ID",
"GOOGLE_ADS_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
"GOOGLE_ADS_REFRESH_TOKEN": "YOUR_REFRESH_TOKEN",
"GOOGLE_ADS_CUSTOMER_ID": "1234567890"
}
}
}
}
docker build -t google-ads-mcp .
docker run --rm \
-e GOOGLE_ADS_DEVELOPER_TOKEN=YOUR_TOKEN \
-e GOOGLE_ADS_CLIENT_ID=YOUR_CLIENT_ID \
-e GOOGLE_ADS_CLIENT_SECRET=YOUR_CLIENT_SECRET \
-e GOOGLE_ADS_REFRESH_TOKEN=YOUR_REFRESH_TOKEN \
-e GOOGLE_ADS_CUSTOMER_ID=1234567890 \
google-ads-mcp
git clone https://github.com/ZLeventer/google-ads-mcp.git
cd google-ads-mcp
npm install
npm run build
MIT — Copyright (c) 2026 Zach Leventer
MCP server for Google Ads — 22 tools for spend diagnosis, impression share, and asset performance.
{ "mcpServers": { "io.github.zleventer-google-ads-mcp": { "command": "npx", "args": [ "-y", "@zleventer/[email protected]" ], "env": { "GOOGLE_ADS_DEVELOPER_TOKEN": "<secret>", "GOOGLE_ADS_CLIENT_ID": "<secret>", "GOOGLE_ADS_CLIENT_SECRET": "<secret>", "GOOGLE_ADS_REFRESH_TOKEN": "<secret>", "GOOGLE_ADS_CUSTOMER_ID": "<value>", "GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<value>" } } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
O publicador lista estas variáveis de ambiente: 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.
Google Ads roda localmente via stdio.
Última verificação: 2026-11-09. MCP server for Google Ads — 22 tools for spend diagnosis, impression share, and asset performance.