Google Ads MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 70 installs a week from npm. Last commit 2 Nov 2026.
Unofficial Google Ads MCP for campaigns, keywords, budgets, and gated mutations.
We read the source, 6 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(command, args, { detached: true, stdio: "ignore" });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add google-ads-mcp -- npx -y google-ads-mcp-unofficial
{
"mcpServers": {
"google-ads-mcp": {
"command": "npx",
"args": [
"-y",
"google-ads-mcp-unofficial"
]
}
}
}
[mcp_servers.google-ads-mcp]
command = "npx"
args = ["-y", "google-ads-mcp-unofficial"]
{
"mcpServers": {
"google-ads-mcp": {
"command": "npx",
"args": [
"-y",
"google-ads-mcp-unofficial"
]
}
}
}
{
"servers": {
"google-ads-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"google-ads-mcp-unofficial"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
GOOGLE_ADS_DEVELOPER_TOKEN (Google Ads API developer token from your Google Ads Manager account. Required), GOOGLE_ADS_CLIENT_ID (Google OAuth2 client ID. Required), GOOGLE_ADS_CLIENT_SECRET (Google OAuth2 client secret. Prefer storing in ~/.google-ads-mcp/config.json via setup), GOOGLE_ADS_LOGIN_CUSTOMER_ID (Manager (MCC) customer ID used as login-customer-id header, no dashes (e.g., 1234567890). Optional but required for multi-account access), GOOGLE_ADS_REDIRECT_URI (OAuth redirect URI. Defaults to http://127.0.0.1:3000/callback), GOOGLE_ADS_TOKEN_PATH (Optional local path for OAuth tokens. Defaults to ~/.google-ads-mcp/tokens.json (0600)), GOOGLE_ADS_PRIVACY_MODE (Optional payload mode: summary, structured, or raw. Defaults to structured. raw returns full Google Ads API payloads), GOOGLE_ADS_ALLOW_MUTATIONS (Set to true to enable write tools (pause/resume keywords/campaigns, set bids, set budgets). Default false (read-only). Agents changing real ad spend is high-stakes; review every change), GOOGLE_ADS_CACHE (Optional SQLite cache toggle. Set to true or sqlite to enable), GOOGLE_ADS_CACHE_PATH (Optional local SQLite cache path. Defaults to ~/.google-ads-mcp/cache.sqlite), GOOGLE_ADS_CACHE_TTL_SECONDS (Optional cache TTL in seconds. Defaults to 60. Set to 0 to keep entries indefinitely (entries are still overwritten on each hit)), GOOGLE_ADS_NO_RETRY (Set to true to disable the HTTP retry middleware. Default false).
MCP server for Google Ads campaign and budget management
Google Ads MCP server — manage campaigns, keywords, and metrics.
Google Ads MCP server. Read campaigns, manage budgets, pause/enable, add negative keywords.
Google Ads MCP with MCC support: 35 tools for campaigns, keywords, reporting, GAQL.
Multi-account Google Ads MCP: campaigns, keywords, search terms, and ad performance.
MCP server for Microsoft Advertising (Bing Ads) — campaigns, keywords, and reports
Google Ads MCP server — query campaigns, keywords, assets & more via natural language
Unofficial MCP server for Google Ads: reporting plus safe draft/confirm campaign management.
Answers built from our own checks of this server.