Integration · Meta Ads
Facebook and Instagram campaigns via MCP.
Meta Ads runs Facebook and Instagram. No first-party MCP, but Pipeboard's hosted server is the strongest path: badged Meta Business Partner, OAuth, full lifecycle in 25+ tools.
Pipeboard's hosted MCP at meta-ads.mcp.pipeboard.co covers the Marketing API end to end: campaigns, ad sets, ads, creatives, audiences, custom audiences, lookalikes, insights, and reporting. The OAuth handshake happens in the cloud (no local token storage). Local OSS alternatives at github.com/pipeboard-co/meta-ads-mcp and brijr/meta-mcp work for teams that prefer self-hosting.
What you can do via MCP
Example prompts the agent runs.
“List my ad accounts and their currency and timezone.”
Calls list_ad_accounts via the Pipeboard MCP and returns the accounts the OAuth scope grants access to, with currency and timezone metadata.
“Show me yesterday's CPM and CTR by ad set in account act_1234567890.”
Pulls insights at the ad-set level for the previous day, returns CPM, CTR, and spend, sorted by CPM descending.
“Find ad creatives with frequency above 3, those are at fatigue risk.”
Filters insights by frequency threshold across active creatives, returns the at-risk creatives plus the campaigns they belong to so the agent can recommend rotation.
“Create a 1% lookalike of my top-customers custom audience.”
Creates the lookalike audience via the Marketing API, returns the audience ID, and reports estimated reach.
“Pause ad sets where ROAS dropped below 2.0 last 7 days.”
Joins insights with ad-set state, identifies underperformers, pauses them via the MCP, and returns the list of paused ad sets with their pre-pause performance.
Insights query plus a programmatic pause on underperformers, both via the Pipeboard hosted MCP.
# Pipeboard hosted MCP, called via the agent runtime
mcp.meta_ads.get_insights({
ad_account_id: "act_1234567890",
level: "ad_set",
date_preset: "last_7d",
fields: ["ad_set_id", "ad_set_name", "spend", "purchase_roas", "frequency"]
})
# Then, for ad sets where ROAS dropped below 2.0:
mcp.meta_ads.update_ad_set({
ad_set_id: "12345678",
status: "PAUSED"
})
# Returns the updated ad set state and pre-pause performance summary.MCP integration
Meta Ads MCP server.
- Server
- https://meta-ads.mcp.pipeboard.co
- Auth
- OAuth (handled in cloud, no local token storage)
- Hosting
- Pipeboard hosted (Streamable HTTP)
- Badged Meta Business Partner; trust path is documented
- 25+ tools spanning campaigns, ad sets, ads, audiences, creatives
- Lookalikes, custom audiences, insights, and reporting all covered
- Local OSS alternatives at github.com/pipeboard-co/meta-ads-mcp and brijr/meta-mcp for self-hosters
Visual demonstration
What this looks like in practice.
- Spend$2,840Impr.412KClicks8,180CTR1.99%CPC$0.35Conv.238
Conversions-Holiday-Audience
Active - Spend$3,160Impr.521KClicks9,490CTR1.82%CPC$0.33Conv.312
Lookalike-1pct-TopCustomers
Active - Spend$1,420Impr.820KClicks3,930CTR0.48%CPC$0.36Conv.42
Reels-Brand-Awareness
Learning - Spend$910Impr.94KClicks2,820CTR3.00%CPC$0.32Conv.184
Retargeting-Cart-Abandoners
Limited - Spend$2,720Impr.490KClicks8,640CTR1.76%CPC$0.31Conv.281
Carousel-Catalog-Sales
Active
9:16 vertical · 30s · 1080x1920
Soda that loves you back.
Adaptogenic ingredients, real fruit, zero sugar. Made for the afternoon slump. Now in 12 stores across the Bay Area.
Frequency 2.4 across the audience; refresh recommended in 7 to 10 days.
CLI alternative
Marketing API REST for non-MCP workflows.
Meta exposes the Marketing API as the canonical programmatic surface. For AI-driven paid-media work the Pipeboard MCP is the primary interface; the REST API fills in for backend automation jobs and historical data exports the agent runtime is not the right place for.
Pairs with these skills
The marketing skill suite.
This integration pairs with the forthcoming paid-media-strategy, ads-creative-development, ads-performance-analytics skills. The skill landing pages and SKILL.md sources land in subsequent dispatches; cross-link hyperlinks are added when the skill pages ship.
Cost considerations
Meta Ads's MCP is free; the platform spend is the cost.
The MCP itself is free or included with your platform plan. The dominant cost lives outside the MCP: ad spend on the platform, compute on the warehouse the platform fronts, or whatever the platform's primary unit of value is.
Pipeboard plan covers the MCP itself. The dominant cost is ad spend on Meta platforms (Facebook + Instagram); the MCP shapes how the agent reads and steers those campaigns.
Recommended patterns
- Treat the agent's API calls as effectively free; the spend the agent triggers (ad spend, platform usage) is the real cost to manage.
- Set platform-side budget caps before letting an agent push changes; an agent that misreads its prompt can spend real money on the platform itself.
- Audit logs matter more than usage dashboards here; read-only agents are safer than full-CRUD agents until the workflow is proven.