Google Ads Manager 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-manager-mcp -- npx -y google-ads-manager-mcp

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

[mcp_servers.google-ads-manager-mcp]
command = "npx"
args = ["-y", "google-ads-manager-mcp"]

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

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

This one needs environment variables set before it will start: GOOGLE_ADS_CLIENT_ID (OAuth client ID from a Google Cloud 'Desktop app' credential), GOOGLE_ADS_CLIENT_SECRET (OAuth client secret from the same Google Cloud credential), GOOGLE_ADS_DEVELOPER_TOKEN (Developer token from Google Ads > Tools & Settings > API Center), GOOGLE_ADS_REFRESH_TOKEN (OAuth refresh token, generated by running `npm run auth`), GOOGLE_ADS_CUSTOMER_ID (The Google Ads account this server manages (10-digit ID, dashes optional)), GOOGLE_ADS_LOGIN_CUSTOMER_ID (Manager (MCC) account ID, only needed if GOOGLE_ADS_CUSTOMER_ID is a client account under a manager account). The author declared them in the registry entry; get the values from the project itself.