Facebook Ads Library MCP Server

Facebook Ads Library MCP server exists for a simple reason — assistants are far more useful when they can act on Facebook Ads Library directly instead of describing what you should do. Get any answer from the Facebook Ads Library, conduct deep research including messaging, creative testing and comparisons in seconds.

What you get

This is a Model Context Protocol (MCP) server for the Facebook Ads Library.

What the assistant can call

Once Facebook Ads Library is connected, these are the calls the assistant has available:

• get_meta_platform_id — Returns platform ID given one or many brand names
• get_meta_ads — Retrieves ads for specific page(s) (platform ID)
• analyze_ad_image — Analyzes ad images for visual elements, text, colors, and composition
• analyze_ad_video — Analyzes single ad video using Gemini AI for comprehensive insights
• analyze_ad_videos_batch — NEW - Analyzes multiple videos in single API call for token efficiency
• get_cache_stats — Gets statistics about cached media (images and videos) and storage usage
• search_cached_media — Searches previously analyzed media by brand, colors, people, or media type
• cleanup_media_cache — Cleans up old cached media files to free disk space
• Prerequisites — The Prerequisites tool exposed by this server

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 2 environment variables: SCRAPECREATORS_API_KEY, GEMINI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.12+ - Anthropic Claude Desktop app (or Cursor) - Pip (Python package manager), install with python -m pip install - An API key for an ads data provider, set as SCRAPECREATORS_API_KEY (see configuration below) - A Google Gemini API key for video analysis (optional, only needed for video ads) > Prefer not to deal with API keys? See the Hosted Version

Choosing this one

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Facebook Ads Library's toolset — get_meta_platform_id, get_meta_ads, analyze_ad_image and 6 more — is a fair guide to whether it matches your workflow.

This entry was verified against Facebook Ads Library's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Facebook Ads Library.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the facebook ads library mcp server does with a few real requests.