MCP.Market

Meta Ad Library Monitor MCP server

by mambabuilt.com·com.mambabuilt/mcp-meta-ad-library-monitor·v1.2.0·1 stars

Find a company active Facebook and Instagram ads through the Meta Ad Library API.

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

1 stars98 downloads/wk

Reviews

Write one

Nobody has reviewed Meta Ad Library Monitor yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Meta Ad Library Monitor tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • find_meta_ads

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identitynamespace and repository owner differ4/10
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Meta Ad Library Monitor compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
98
more than 62% of 12,191 servers with a package

What its tools let an agent do: 1 read

Release history: 3 versions in the registry since 2026-08-24, latest 2026-10-16, typically one every 43 days.

Install Meta Ad Library Monitor in Claude Code, Cursor or VS Code

Runs npx -y @mambalabsdev/mcp-meta-ad-library-monitor on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-meta-ad-library-monitor -- npx -y @mambalabsdev/mcp-meta-ad-library-monitor
Add to Cursor

What the publisher says

From the Meta Ad Library Monitor repository's README, as published. We do not edit it. Read it on GitHub

Meta Ad Library Monitor MCP Server

An MCP server that finds a company's active Facebook and Instagram ads through the Meta Ad Library API. It wraps the Mamba Labs Meta Ad Library Monitor actor on Apify and returns Clay-ready flat JSON rows to any MCP client.

What's Inside

  • What it does
  • Quick start
  • Prerequisites
  • Example prompts
  • Inputs
  • Output
  • Example output
  • Features
  • Full actor documentation
  • Mamba Labs GTM Suite
  • License

What it does

Give it a company name or domain and your own Meta access token, and it searches the Meta Ad Library and returns one flat row per ad: creative text, headline, delivery dates, the Meta surfaces the ad ran on, and Meta's permanent snapshot URL for the rendered ad.

Read the coverage first, because it decides whether this tool is any use to you. It reads Meta's Ad Library Graph API, which is the only route Meta sanctions, and that API publishes two things: every ad delivered to an audience in the EU, whatever the ad is about, and social issue, election and politics ads worldwide. So an EU heavy list gets good coverage of ordinary commercial advertising, while a US or UK list of ordinary product ads mostly comes back not_found. That is Meta's dataset rather than a fault in the lookup, and every row carries a coverage note saying what the search could have found. Impressions and spend exist for political ads only and arrive as bands, so a null there is not zero spend.

All of the searching runs on Apify. This package is a thin client that calls the actor and hands back the result unchanged.

Quick start

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

Add this to your Claude Desktop config:

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

Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The findmetaads tool will be available.

You also need your own Meta app access token, free to create at developers.facebook.com. It is passed as a tool argument rather than an environment variable, so the model supplies it per call.

Prerequisites

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Meta Ad Library Monitor: common questions

Is Meta Ad Library Monitor MCP server safe?
Mostly: it is graded B (77/100). Read the Meta Ad Library Monitor safety report
How do I install Meta Ad Library Monitor?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Meta Ad Library Monitor need an API key?
Yes. The registry entry asks for APIFY_TOKEN.
Is Meta Ad Library Monitor maintained?
The last commit was 8 days ago (2026-10-27). The latest release is v1.2.0.
How does Meta Ad Library Monitor compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from mambabuilt.com →