Google Ads MCP server
Turn Google Ads questions into useful answers.
Explore performance, research keywords and prepare campaign changes from your MCP client.
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @getmcpads/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
GOOGLE_ADS_DEVELOPER_TOKEN=<secret> GOOGLE_ADS_CLIENT_ID=<value> GOOGLE_ADS_CLIENT_SECRET=<secret> GOOGLE_ADS_REFRESH_TOKEN=<secret> GOOGLE_ADS_LOGIN_CUSTOMER_ID=<value> GOOGLE_ADS_ACCOUNT_IDS=<value> GOOGLE_ADS_ENABLE_WRITES=<value> claude mcp add com.getmcpads-google-ads -- npx -y @getmcpads/google-ads-mcp-server@2.1.2รันในเทอร์มินัล
{ "mcpServers": { "com.getmcpads-google-ads": { "command": "npx", "args": [ "-y", "@getmcpads/[email protected]" ], "env": { "GOOGLE_ADS_DEVELOPER_TOKEN": "<secret>", "GOOGLE_ADS_CLIENT_ID": "<value>", "GOOGLE_ADS_CLIENT_SECRET": "<secret>", "GOOGLE_ADS_REFRESH_TOKEN": "<secret>", "GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<value>", "GOOGLE_ADS_ACCOUNT_IDS": "<value>", "GOOGLE_ADS_ENABLE_WRITES": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน 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.
เปิดThe film shows hosted getmcpads with sample data. Its MCP Apps, from creative galleries and alerts to Google Sheets exports and bulk launches, belong to the hosted product. This repository provides the standalone native API tools.
35 read tools · 10 write tools, disabled by default.
Run locally with your own platform credentials and a client that supports stdio MCP, such as Claude Desktop, Claude Code or Cursor. Your requests go directly to the platform. For managed connections, including supported ChatGPT setups, use the hosted option.
v2.0.1: Native tools and security update · September 20, 2026
Requires Node.js 22.12 or newer. CI covers Node 22 and 24. Version 2.0.1 drops Node 18 and 20 support. Read the current tool schemas before reusing saved arguments. Writes remain optional and require explicit confirmation. Hosted creative integrations and MCP Apps UI are outside this release.
This is a GitHub source release. npm and MCP Registry versions are published separately. The commands below select this exact version; unpinned npx examples later in this document select the version currently available on npm.
git clone --branch v2.0.1 --depth 1 https://github.com/get-mcp-ads/google-ads-mcp-server.git
cd google-ads-mcp-server
npm ci
npm run build
Configure your MCP client to run node with the absolute path to dist/cli.js and the platform credentials documented below.
Prefer a managed connection? Use Google Ads with hosted getmcpads. Connect your account, select the data your assistant may access and use the hosted MCP connection. See the site for current features and plans.
The Google Ads API is queried with GAQL, its own query language, and most of its surface is
only reachable that way. This server carries the metric and dimension catalogues, so the model
asks for cost and conversions by name and the server writes the query.
google_ads_validate_query lets it check a combination before spending a call on it, and
google_ads_run_gaql is still there when you want to write GAQL yourself.
Keyword ideas, historical volumes and forecasts live in a separate RPC service that GAQL
cannot reach at all. Same for Reach Planner, audience insights and benchmarks. This server
covers them through google_ads_run_readonly_rpc and dedicated tools.
This is the heaviest setup of any advertising platform. Four values are needed, and one of them requires a review by Google. Budget an hour the first time.
From a manager (MCC) account, open Tools → API Center and apply for a token. It starts at Test Account level, which only reaches test accounts. Apply for Basic Access to reach live accounts. Google reviews the application, which can take a few days.
In a Google Cloud project, enable the Google Ads API, then create an OAuth client under APIs & Services → Credentials. Choose Desktop app for local use. Note the client ID and client secret.
Run the OAuth consent flow once, signed in as the Google account that can see your ad accounts, and keep the refresh token it returns. Google's own helper script does this in one command.
The refresh token does not expire. It is the sensitive value here: anyone holding it can mint access tokens indefinitely. Treat it like a password, and use an OAuth client dedicated to this server so you can revoke it on its own.
If the accounts you query sit under an MCC, set GOOGLE_ADS_LOGIN_CUSTOMER_ID to the manager
account ID. Dashes are accepted and stripped. Skip it for a standalone account.
You can also leave it unset. Google refuses any request against a managed account unless the
call names its manager, with a USER_PERMISSION_DENIED that mentions neither the account nor
the manager, so it reads as missing access rather than as a missing header. When the variable
is unset and the account you query is not directly accessible, the server asks the managers it
can reach which accounts they hold, and announces the one that holds yours. The answer is
resolved once and kept for the life of the process.
Setting the variable is still faster: it skips that discovery entirely, and it is the right choice when every account you query sits under the same MCC.
Run google_ads_health_check as your first call. It verifies all four credentials, lists
the accounts you can actually reach, and reports what is missing, without printing any secret.
~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"google-ads": {
"command": "npx",
"args": ["-y", "@getmcpads/google-ads-mcp-server"],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "your-developer-token",
"GOOGLE_ADS_CLIENT_ID": "your-client-id",
"GOOGLE_ADS_CLIENT_SECRET": "your-client-secret",
"GOOGLE_ADS_REFRESH_TOKEN": "your-refresh-token"
}
}
}
}
Restart Claude Desktop. Ask it: "list my Google Ads accounts".
claude mcp add google-ads --env GOOGLE_ADS_DEVELOPER_TOKEN=... --env GOOGLE_ADS_CLIENT_ID=... --env GOOGLE_ADS_CLIENT_SECRET=... --env GOOGLE_ADS_REFRESH_TOKEN=... -- npx -y @getmcpads/google-ads-mcp-server
.cursor/mcp.json in your project, same shape as the Claude Desktop config above.
git clone https://github.com/get-mcp-ads/google-ads-mcp-server.git
cd google-ads-mcp-server
npm install && npm run build
cp .env.example .env # then fill in your credentials
npm start
Check your setup at any time:
npm run doctor
Write tools are disabled by default. Enable them with GOOGLE_ADS_ENABLE_WRITES=1.
Google's own server has none at all, so this is the part to read carefully.
When enabled, every write tool returns a preview and changes nothing:
// google_ads_update_campaign_budget { customerId: "123-456-7890", budgetId: "555", dailyAmount: 50 }
{
"applied": false,
"action": "google_ads_update_campaign_budget",
"change": { "customer": "1234567890", "budget": "555",
"newDailyBudget": 50, "inMicros": 50000000 },
"message": "Preview only, nothing was changed. Repeat the same call with confirm: true to apply this change to the live account."
}
Only a second call carrying confirm: true touches the live account.
This is deliberate. An assistant composes these calls, and it can pick the wrong customer, the wrong campaign, or the wrong order of magnitude on a budget. A mandatory preview makes the mistake visible before it costs money, and gives a human the stopping point the protocol does not guarantee on its own.
Two further guardrails:
google_ads_create_campaign always creates the campaign PAUSED. There is no option to
create it active. Someone has to look at it before it spends.12500000. The preview shows both, so a factor-of-a-thousand
mistake is visible before it applies.Every tool is listed below. See server-card.json for complete parameter and output schemas.
Disabled by default. Calls preview unless explicitly confirmed. Check the configuration and exact schema before use.
This server holds a refresh token that never expires, a client secret and a developer token. Concretely:
googleads.googleapis.com and
oauth2.googleapis.com. A test fails the build if a third host appears in the source.redirect: "error", so a redirect
cannot forward a bearer token or client secret to another host. A test fails the build if
any fetch omits this.Full policy and reporting instructions: SECURITY.md.
Try hosted Google Ads if you want to use this source without operating a local server. getmcpads also connects advertising, Search Console and GA4 through one MCP URL. Source availability and plan limits are listed on the site; connecting an account is still required.
See the current hosted tool catalogue and pricing before choosing a paid plan. This Apache 2.0 adapter remains independently useful with your own credentials.
Issues and pull requests are welcome. See CONTRIBUTING.md. Please read SECURITY.md before reporting anything security-related.
Apache License 2.0. See also NOTICE.
Google, Google Ads and the Google Ads API are trademarks of Google LLC. This project is not affiliated with, endorsed by, or sponsored by Google LLC. It is an independent client of a public API.
Every tool declares read/write annotations, parameter descriptions and a structured output schema. Successful calls expose the payload as structuredContent.result; errors retain isError: true. The generated server card contains definitions only.
Run npm run bundle -- /path/to/output to build a .mcpb desktop bundle from the current catalog. Credentials are entered locally during installation. Write tools remain disabled unless explicitly enabled.
Maintained by Emmanuel at getmcpads. Questions: [email protected].
Google Ads MCP server: 35 read tools, 13 opt-in preview-first writes.
{ "mcpServers": { "com.getmcpads-google-ads": { "command": "npx", "args": [ "-y", "@getmcpads/[email protected]" ], "env": { "GOOGLE_ADS_DEVELOPER_TOKEN": "<secret>", "GOOGLE_ADS_CLIENT_ID": "<value>", "GOOGLE_ADS_CLIENT_SECRET": "<secret>", "GOOGLE_ADS_REFRESH_TOKEN": "<secret>", "GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<value>", "GOOGLE_ADS_ACCOUNT_IDS": "<value>", "GOOGLE_ADS_ENABLE_WRITES": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_REFRESH_TOKEN, GOOGLE_ADS_LOGIN_CUSTOMER_ID, GOOGLE_ADS_ACCOUNT_IDS, GOOGLE_ADS_ENABLE_WRITES
Google Ads ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-15 Google Ads MCP server: 35 read tools, 13 opt-in preview-first writes.