Back to Directory/Search & Knowledge

com.mambabuilt/mcp-google-ads-transparency-monitor

List the Google ads a company runs, from the Ads Transparency Center, with a company summary.

Search & KnowledgeTypeScriptv1.0.1

Google Ads Transparency Monitor MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

An MCP server for the Mamba Labs Google Ads Transparency Monitor actor on Apify. Give it a company domain or an advertiser name. Each run reads Google's public Ads Transparency Center and returns one row per ad, with the format, first and last shown dates, a creative link, and the ad's page, plus a company summary row with Google's total ad count band.

What's Inside

What it does

List the Google ads a company runs. Give a company domain (for example stripe.com) or an advertiser name, or lists of either. You get one row per ad with the advertiser, ad ID, format (text, image, or video), first and last shown dates, a creative link, and the ad's Transparency Center page, plus one summary row per input that says whether the company runs Google ads, how many (Google's own count band, for example 8,000 to 9,000), and in which formats. Rows with no ads, blocked requests, or a changed Google page come back free with a row_status saying so.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-google-ads-transparency-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-google-ads-transparency-monitor"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The get_google_ads tool appears.

Prerequisites

Example prompts

  • "Does notion.so run Google ads? How many, and in which formats?"
  • "Show me the 10 most recent video ads HubSpot ran in the US."
  • "For stripe.com, ramp.com, and brex.com, which ones advertised on Google in the last 30 days?"

Tool

get_google_ads. One tool. Example arguments:

{
  "company_domain": "stripe.com",
  "max_ads": "20",
  "since_days": "90"
}

Inputs

Every buyer facing input of the live actor, unchanged. Omitted inputs take the actor's own defaults. Give one of company_domain, advertiser_name, domains, or advertiser_names.

InputTypeRequiredDescription
company_domainstringnoA company website domain, for example stripe.com.
advertiser_namestringnoAn advertiser name as Google verifies it, for example Stripe, Inc.
domainsarraynoSeveral company domains. Up to 500 inputs per run.
advertiser_namesarraynoSeveral advertiser names.
regionstringnoanywhere, or a two letter country code such as US, GB, DE, or FR. Default anywhere.
formatsarraynotext, image, video. Omit for all formats.
max_adsstringnoAd rows per input, 1 to 1000. Default 50.
since_daysstringnoOnly ads last shown in this many days; 0 for all. Default 90.
include_summarystringnotrue or false. Default true.
max_charge_usdstringnoOptional cost cap for the run.
skipCachestringnotrue reads fresh results instead of the free 24 hour cache. Default false.
proxy_modestringnoauto, direct, or residential. Default auto.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
ad-found, per ad row returned$0.002$0.0019$0.0018$0.0017
company-summary, per input with ads$0.003$0.00285$0.0027$0.00255
apify-actor-start, per run start$0.0005$0.0005$0.0005$0.0005

Rows with no ads, blocked rows, changed source rows, error rows, and cached rows are free.

Your keys

The actor needs no provider key. It reads Google's public Ads Transparency Center and holds no key of its own. If a run uses the Apify proxy, that traffic adds nothing to your price: Mamba Labs pays the platform costs of the run. proxy_mode is a reliability setting.

Full actor documentation

apify.com/mambalabs/google-ads-transparency-monitor

License

MIT. See LICENSE.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y @mambalabsdev/mcp-google-ads-transparency-monitor

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "com-mambabuilt-mcp-google-ads-transparency-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-google-ads-transparency-monitor"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@mambalabsdev/mcp-google-ads-transparency-monitornpm

Compatible MCP Clients

com.mambabuilt/mcp-google-ads-transparency-monitor works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More