Adextract MCP Server

Adextract MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Adextract MCP directly instead of describing what you should do. Search Meta, Google Ads, LinkedIn, and TikTok ad libraries plus creative analysis via MCP.

What you get

Connect AI assistants to Adextract — search ad libraries across Meta, Google Ads, LinkedIn, and TikTok, plus creative analysis with ad_reader.

What the assistant can call

Once Adextract MCP is connected, these are the calls the assistant has available:

• search_meta_ads — Meta
• search_meta_pages — Meta
• get_meta_page_info — Meta
• get_meta_ad_details — Meta
• search_google_ads — Google
• search_google_ads_advertisers — Google
• get_google_ad_details — Google
• get_google_ads_advertiser_info — Google
• search_linkedin_ads — LinkedIn
• search_tiktok_ads — TikTok
• search_tiktok_advertisers — TikTok
• get_tiktok_ad_details — TikTok

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 one environment variable: YOUR_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.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Adextract MCP's toolset — search_meta_ads, search_meta_pages, get_meta_page_info and 11 more — is a fair guide to whether it matches your workflow. It is maintained by anuragind003; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Adextract MCP'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 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Adextract MCP.
• 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 adextract mcp mcp server does with a few real requests.