Skip to content
Facebook Leads logo

Facebook Leads MCP server

Capture leads from Facebook

Facebook Leads is not a separate install. One Activepieces MCP server exposes it alongside 770+ other apps, behind a single URL.

Tools
1
Works with
Any MCP client
Auth
OAuth 2.0
License
MIT, open source
Updated
October 2026

About the Facebook Leads MCP server

Connect Facebook Leads once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Facebook Leads and 770+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Facebook Leads tools your AI can run

Once connected, your assistant can call any of these Facebook Leads actions by asking in plain language.

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Facebook Leads events your agent can watch

These start a run the moment something happens in Facebook Leads, so work gets picked up on its own.

  • New Lead

    Triggers when someone fills in one of your lead ad forms.

    3 fields

Give your assistant Facebook Leads

Connect Facebook Leads once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 770+ other apps. Free to start.

Facebook Leads MCP, answered.

No. That is the point of it. One Activepieces server exposes Facebook Leads alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Facebook Leads in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 1 tool, including Custom API Call, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.