Google Ads Monitor

io.github.sumitrmardyPublished by GitHub account sumitrmardyv1.0.0Updated Oct 27, 2026

Competitor Google ads from the Ads Transparency Center: new ads since last run, with ad copy.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Apify-hosted MCP server that lets an assistant pull competitors' new Google ads, with ad copy, from the Ads Transparency Center.

What you can do
  • Retrieve competitor Google ads from the Ads Transparency Center.
  • Surface ads that are new since the previous run.
  • Return the ad copy alongside the ads found.
When to use it
Useful for competitive ad research or monitoring: checking what new Google ads competitors have launched since the last check, and reading their copy. Suited to marketing and competitive-intelligence workflows rather than general browsing.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com; no local package to install. OAuth sign-in is required. Clients without OAuth can instead send an Apify API token as a Bearer value in the Authorization header.
Before you install
The server needs an Apify account and either OAuth or an Apify API token in the Authorization header; treat that token as a secret. Usage may consume Apify platform credits, so check your plan. Ad data comes from Google's Ads Transparency Center and is passed through Apify.

Installation

In SourceWeft

  1. Open Google Ads Monitor in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.sumitrmardy%2Fgoogle-ads-monitor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "google-ads-monitor": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=sumitr_mardy/google-ads-monitor"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 21, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.