MCP server
Meta Ads MCP Server
The same AdWhiz connection that reaches Google Ads also reaches Meta. 33 tools cover the Facebook and Instagram ad stack — campaigns, ad sets, ads, creatives and audiences — plus the insights needed to judge whether any of it is working.
Hosted endpoint — Streamable HTTP, nothing to install
https://mcp.adwhiz.ai/mcpWhat the 33 Meta Ads tools cover
Meta's structure is not Google's, and the tools follow Meta's: ad sets rather than ad groups, audiences rather than keywords, creatives as first-class objects.
Campaigns, ad sets and ads
Create all three levels, change status at each, update settings, and duplicate an existing campaign as a starting point.
Creatives and media
Upload ad images and partnership videos, build ad creatives from them, and read back the creatives already attached to an ad.
Custom and lookalike audiences
Create custom audiences, build lookalikes from them, and estimate the reach of a targeting spec before committing budget to it.
Targeting research
Search Meta's interest taxonomy and geo location database to find the exact targeting identifiers, instead of guessing at names.
Insights at four levels
Pull performance at account, campaign, ad set and ad level, so a question about which ad set is dragging can be answered without exporting anything.
Budgets and bulk changes
Update campaign budgets, and apply status changes across campaigns, ad sets and ads without clicking through Ads Manager.
Organic context
Read the account's Pages, Instagram media and post comments — useful when the creative that is working organically is the one worth promoting.
Audit and change history
Run a mini account audit for structural problems, and read the change history to see what moved and when.
Connecting a client
This page is about what the server does. Wiring a specific client to it is a separate, short job — each guide has the exact config that client expects.
Managing search alongside social? See the Google Ads MCP server.
Meta Ads MCP questions
No. One MCP connection reaches both. Connect a Google Ads account, a Meta account, or both — the tool list your client sees reflects what you have linked.
It creates them. Campaigns, ad sets, ads and creatives can all be created, and images and videos can be uploaded through the same connection.
Both — they are one ad system. There are also tools for reading Instagram media and post comments, which sit outside the ad objects themselves.
Only the ad accounts you connect are reachable, dry-run mode shows the call before it runs, and every write is recorded in a mutation log. Those apply the same way whichever client is driving.
No. It is hosted at mcp.adwhiz.ai over Streamable HTTP. There is no SSE endpoint and no local process.
Any MCP client that supports remote servers over Streamable HTTP. Guides exist for Claude Code, Claude app, Cursor, Windsurf, OpenClaw, Hermes and Grok.
Usually yes, and it is worth being precise. A Meta MCP server in this sense is an MCP server that reaches the Meta advertising API, which is what this is. It is not an MCP server published by Meta itself, and it has nothing to do with Meta's Llama or hardware work. If you are searching for a way to drive Facebook and Instagram ad campaigns from an AI client, this is the thing you mean.
Run Facebook and Instagram from the same agent
Connect a Meta ad account, pick a client, and start with an insights question before granting write access.
Leave your email and our team will help you set up and troubleshoot.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.