MCP Tools DirectoryAbout this integration
Find a company active Facebook and Instagram ads through the Meta Ad Library API.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.0.1
- Package
- @mambalabsdev/mcp-meta-ad-library-monitor
- Last compatibility test
- Not independently tested
Connect your agent
@mambalabsdev/mcp-meta-ad-library-monitorPublisher README and executable manifest reviewed from the pinned captures. The package, Apify actor and Meta API were not executed. A Meta token is passed as a tool argument according to the publisher, and coverage is constrained by Meta's dataset.
Capabilities: Search the documented Meta Ad Library coverage, Return ad creative metadata and snapshot URLs, Filter by geography, activity state and media type
Connected profiles
Additional details
com.mambabuilt/mcp-meta-ad-library-monitor
Source ↗ · Checked 2026-09-171.0.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17APIFY_TOKEN
Source ↗ · Checked 2026-09-17@mambalabsdev/mcp-meta-ad-library-monitor
Source ↗ · Checked 2026-09-191.0.1
Source ↗ · Checked 2026-09-19The publisher documents Node.js 18+ and a Claude Desktop command that launches the package with npx as a persistent MCP subprocess.
Source ↗ · Checked 2026-09-19The wrapper requires APIFY_TOKEN, while searches also require the caller's Meta app access token supplied per tool call; political-ad access can additionally require Meta identity verification.
Source ↗ · Checked 2026-09-19The local command-launched wrapper sends searches to an Apify actor that calls Meta's Ad Library API; the existing stdio connection identity is preserved.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19