All 35 tools read: insights at every level of the hierarchy, creative and image lookups, activity logs, and the interest, behavior, demographic and geo catalogs a targeting spec draws on. None of them alters a campaign — creating and editing sit behind META_ADS_ENABLE_WRITE_TOOLS. The insight and record tools take an explicit fields list, so naming the metrics you want keeps a response to a workable size.
An MCP server over Meta's Graph API advertising endpoints — ad accounts, campaigns, ad sets, ads, creatives, activity logs and the targeting search catalogs
- Performance insights at account, campaign, ad set and ad level, each taking demographic breakdowns, attribution windows and either a date preset or an explicit time range.
- Hierarchy walks in both directions: campaigns by account, ad sets by account or by campaign, ads by account, campaign or ad set — all with status filters and pagination.
- Creative inspection — creatives by account or by ad, image lookup by hash, ad video source and thumbnail, and placement previews returned as links or embed HTML.
- Targeting research before anything is spent: keyword search over interests, suggestions from a seed list, behavior and demographic catalogs, geo search, and an audience-size estimate for a full targeting spec.
- Change history for an account or an ad set — status changes, budget updates, targeting edits — covering one week by default.
- meta_ads_compute_image_crops returns centered crop coordinates for the aspect-ratio keys Meta accepts, and meta_ads_fetch_pagination_url follows a paging URL when a response is cut short.
A Meta ad account and a Facebook user whose token reaches it, supplied as META_ADS_ACCESS_TOKEN, together with META_ADS_ENABLE_WRITE_TOOLS, the flag for the write tools.
One command plus a key — npx meta-ads-mcp-server --access-token YOUR_META_ACCESS_TOKEN, then supply credentials