Google Ads MCP Server

Connect this server

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 @zleventer/google-ads-mcp

{
  "mcpServers": {
    "google-ads-mcp": {
      "args": [
        "-y",
        "@zleventer/google-ads-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.google-ads-mcp]
command = "npx"
args = ["-y", "@zleventer/google-ads-mcp"]

{
  "mcpServers": {
    "google-ads-mcp": {
      "args": [
        "-y",
        "@zleventer/google-ads-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "google-ads-mcp": {
      "args": [
        "-y",
        "@zleventer/google-ads-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: GOOGLE_ADS_DEVELOPER_TOKEN (Google Ads developer token (apply at https://developers.google.com/google-ads/api/docs/get-started/dev-token)), GOOGLE_ADS_CLIENT_ID (OAuth 2.0 client ID from Google Cloud Console), GOOGLE_ADS_CLIENT_SECRET (OAuth 2.0 client secret from Google Cloud Console), GOOGLE_ADS_REFRESH_TOKEN (OAuth 2.0 refresh token with https://www.googleapis.com/auth/adwords scope), GOOGLE_ADS_CUSTOMER_ID (Default Google Ads customer ID (numeric, no dashes). Can be overridden per tool call.), GOOGLE_ADS_LOGIN_CUSTOMER_ID (Manager (MCC) account ID — required only if accessing accounts under an MCC). The author declared them in the registry entry; get the values from the project itself.