Facebook Advertisers Leads

io.github.BerrkaydevPublished by GitHub account Berrkaydevv1.0.0Updated Nov 21, 2026

Businesses running Meta ads for a trade and country, with website audit and contacts.

The publisher's own server: Finder Jobs

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Apify-hosted remote MCP server that finds businesses running Meta ads by trade and country, with website audit and contact details.

What you can do
  • Find businesses that run Meta ads, filtered by trade and country.
  • Retrieve website audit results and contact details for the businesses found.
  • Return lead-style prospect lists for outreach.
  • No individual tools are documented in the supplied listing, so exact operations are not confirmed.
When to use it
Useful when you want an assistant to build prospect or lead lists of advertisers on Meta for a specific industry and market, for example for sales outreach or market research.
Requirements
Remote MCP endpoint at mcp.apify.com over streamable HTTP. Requires an Apify account and an Apify API token sent in the Authorization header as a Bearer token. Runs are billed to that Apify account.
Before you install
The Authorization header carries an Apify API token, a secret that should be kept private. Runs consume paid Apify credits, so usage costs money. Results include business contact details, which may be subject to privacy and marketing regulations where you operate.

Installation

In SourceWeft

  1. Open Facebook Advertisers Leads 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.Berrkaydev%2Fmeta-ad-library-lead-finder/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": {
    "facebook-advertisers-leads": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=berkaydev/meta-ad-library-lead-finder"
    }
  }
}

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.0LatestNov 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.

Other Finder integrations