DEV Community

Rupa Tiwari
Rupa Tiwari

Posted on • Originally published at mcpplaygroundonline.com

How to Automate Meta Ads with Claude AI and MCP — Real Workflows, Real Results

The era of manually exporting CSVs to analyze ad performance is over. Here's what's replacing it.


If you manage Meta advertising campaigns, you know the drill.

Export performance data. Open a spreadsheet. Manually calculate ROAS by ad set. Stare at frequency numbers trying to judge whether creative fatigue is setting in. Shift budgets. Wait three days to see if it worked. Repeat.

It's not that this process doesn't work — it does. It's that it's slow, reactive, and completely dependent on when you have time to look at the data. By the time you catch a creative burning out or a budget leaking into a non-converting audience, you've already lost money.

That's changing. A combination of Claude AI and the Meta Ads MCP server is now giving marketers — from solo operators to agency teams managing millions in spend — something genuinely new: an AI assistant that has live access to your campaign data and can act on it through natural conversation.

This isn't about AI writing your ad copy. This is about AI running the operational layer of your campaign management.


What Is the Meta Ads MCP Server?

The Meta Ads MCP server is an open-source Model Context Protocol server built by Pipeboard that bridges Claude AI directly to the Meta Marketing API.

Instead of Claude reasoning about your campaigns from a screenshot or a pasted CSV, it has a live, authenticated connection to your actual ad account data — campaigns, ad sets, creatives, audiences, insights, and budget schedules. All of it, in real time.

Once connected, Claude can:

  • Pull live performance metrics (CTR, ROAS, CPC, Frequency, CPM) without any export
  • Read your campaign structure across all accounts
  • Create, update, and pause campaigns and ad sets
  • Search and validate audience interests and demographics
  • Upload creatives and manage ad copy variations
  • Detect performance anomalies and flag them before they compound

The protocol uses JSON-RPC 2.0 under the hood — the same open standard that the broader MCP ecosystem is built on. What that means practically: you don't manage an integration. You have a conversation.


The Tools Available (What Claude Can Actually Do)

The meta-ads-mcp server exposes 25 tools across six functional areas. Here's what each area covers:

Account & Campaign Management

Tool What It Does
get_ad_accounts List all ad accounts your token has access to
get_campaigns Fetch all campaigns with optional status filtering
create_campaign Launch a new campaign with objective and budget
get_campaign_details Pull full details on any specific campaign

Ad Set Operations

Tool What It Does
get_adsets Retrieve ad sets, filter by campaign
create_adset Create a new ad set with targeting and bidding
update_adset Modify frequency caps, bid strategy, schedule
get_adset_details Deep-dive into any ad set's configuration

Creative Management

Tool What It Does
get_ad_creatives Retrieve creative details for any ad
create_ad_creative Build new creatives with image and copy
update_ad_creative Revise creative content
upload_ad_image Upload images directly for use in ads
get_ad_image Download and visually inspect a live ad image

Performance Analytics

Tool What It Does
get_insights Pull performance data for any account, campaign, ad set, or individual ad with custom date ranges

Audience & Targeting

Tool What It Does
search_interests Find interest targeting options by keyword
get_interest_suggestions Get interest recommendations based on existing selections
validate_interests Confirm interest names or IDs are valid before use
search_behaviors Access behavior targeting specifications
search_demographics Retrieve demographic targeting options
search_geo_locations Find geographic targeting by country, city, or region

Budget & Scheduling

Tool What It Does
create_budget_schedule Set up budget allocations for specific time windows

How to Connect It: Three Setup Options

Option 1 — Remote MCP via Pipeboard (Fastest, Paid)

Time: ~5 minutes | Cost: $49/month

Pipeboard hosts and manages the MCP server for you. You authorize your Meta Business Manager, get a server URL, and paste it into Claude Desktop's config. No Node.js, no terminal, no infrastructure.

Best for: marketers, agencies, non-technical teams who want it running today.

Option 2 — Local Installation (Free, Open Source)

Time: 30–60 minutes | Cost: Free

# Prerequisites: Node.js 18+
git clone https://github.com/pipeboard-co/meta-ads-mcp
cd meta-ads-mcp
npm install

# Authenticate with Meta
bash meta_ads_auth.sh

# Add to Claude Desktop config (~/.config/claude/claude_desktop_config.json)
{
  "mcpServers": {
    "meta-ads": {
      "command": "node",
      "args": ["/path/to/meta-ads-mcp/index.js"],
      "env": {
        "META_ACCESS_TOKEN": "your_access_token_here"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Best for: developers, technical marketers, teams who want full control and zero ongoing cost.

Option 3 — Composio (Managed, Developer-Friendly)

Time: ~10 minutes | Cost: Usage-based

Composio provides a managed Meta Ads MCP integration with pre-built authentication. Good middle ground between fully managed and fully self-hosted.

Before committing to any setup: You can explore how MCP servers work and what tools they expose at MCP Playground Online — paste any MCP server URL and inspect its tools in your browser, no install needed.


Real Workflows: What This Actually Looks Like

Workflow 1: Morning Campaign Audit (What Used to Take 2 Hours)

The old way:

  • Log into Meta Ads Manager
  • Export data for each campaign
  • Open spreadsheet
  • Calculate performance by ad set
  • Identify outliers
  • Make a mental plan
  • Go back to Meta and implement changes
  • Total time: 90–120 minutes

The new way:

You: "Give me a full performance summary of all active campaigns
for the last 7 days. Flag anything with ROAS below 2.0 or
frequency above 3.5."

Claude: [Pulls live data via get_insights, get_campaigns]

"Here's your summary across 8 active campaigns:

🔴 NEEDS ATTENTION:
- 'Retargeting — Warm Audience' — Frequency: 4.2, ROAS: 1.4
  Recommendation: Pause or refresh creative. Audience is fatigued.

- 'Lookalike 5% — Purchase' — ROAS: 1.7, CPC up 34% week-over-week
  Recommendation: Review creative. Consider tightening audience.

✅ PERFORMING:
- 'TOF — Interest Stack A' — ROAS: 4.1, Frequency: 1.8
  Recommendation: Budget increase candidate.

- 'TOF — Broad Auto' — ROAS: 3.6, CPA: $18.40 (target: $22)
  Recommendation: Maintain. Room to scale."
Enter fullscreen mode Exit fullscreen mode

Total time: 45 seconds.


Workflow 2: Creative Fatigue Detection — Before You Lose Money

Creative fatigue is the silent budget killer in Meta campaigns. Most advertisers only notice it when ROAS has already dropped significantly. By then, the damage is done.

With Claude connected to live Meta data, you can catch it on the way down, not after.

Real example from the field:

A DTC fitness brand was running a top-performing ad at $180/day. Historical data showed their creatives typically peaked around day 8–10 before CTR began decaying.

With the Meta Ads MCP integration:

  • Claude monitored CTR trend daily (via get_insights)
  • On day 6, CTR had dropped 18% from its peak — within the creative's normal variance range, but at an earlier-than-expected rate
  • Claude flagged it: "CTR trending down faster than your historical baseline for this placement. Recommend preparing creative refresh before frequency reaches 2.8."
  • The brand launched a refreshed angle on day 7
  • Result: maintained 3.2x ROAS through day 14, instead of the typical decay to 1.8x they'd been experiencing previously

The workflow prompt:

"Check CTR trend for all ads in the 'TOF Prospecting' campaign
over the last 14 days. Flag any where CTR has dropped more than
15% from its 3-day peak, and show me the current frequency for those ads."
Enter fullscreen mode Exit fullscreen mode

Workflow 3: Budget Reallocation Based on Live ROAS

The problem most advertisers have:
They set budgets based on intuition or historical performance, then leave them running for days or weeks without rebalancing — even when the data clearly shows where money should move.

Real example:

A SaaS company was running $3,000/day split evenly across 5 campaigns — $600 per campaign. Claude's analysis via get_insights revealed:

  • 2 campaigns were delivering 80% of all conversions at 40% below target CPA
  • 3 campaigns were consistently running 60% above target CPA with no improving trend

The reallocation Claude recommended:

Campaign Before After Reason
TOF — Broad $600 $900 Strong ROAS, not spend-constrained
Retargeting — Purchasers $600 $750 Highest ROAS of all campaigns
Lookalike — 1% $600 $600 Stable, maintain
Interest Stack B $600 $450 Above target CPA, limit exposure
Interest Stack C $600 $300 Consistently underperforming, monitor

Outcome: Monthly qualified demo bookings went from 147 to 231 — with identical total spend. No new creative. No new audiences. Just smarter money distribution backed by live data.


Workflow 4: Audience Discovery and Interest Validation

One of the most underused capabilities: Claude can search and validate Meta's entire interest graph before you waste budget on poorly matched audiences.

You: "I'm launching a campaign for a B2B project management tool
targeting SMB owners. Suggest 10 interest targeting options,
validate they exist in Meta's system, and estimate audience size."

Claude: [Calls search_interests, validate_interests, get_interest_suggestions]

"Here are 10 validated interests for your campaign:

1. Small Business (Audience: 180M) — Broad but relevant
2. Entrepreneurship (Audience: 87M) — Strong intent signal
3. Project Management (Audience: 23M) — High relevance, smaller pool
4. Asana (Audience: 4.2M) — Competitor targeting, strong intent
5. Trello (Audience: 6.8M) — Competitor targeting
6. Monday.com (Audience: 3.1M) — Competitor targeting, high intent
7. Business productivity (Audience: 41M) — Medium relevance
8. Startup (Audience: 52M) — Overlaps with entrepreneurship
9. SaaS (Audience: 8.3M) — B2B signal
10. Remote work (Audience: 67M) — Post-2020 behavioral signal

Recommended approach: Start with interests 3, 4, 5, 6 stacked —
total addressable audience ~37M, all showing commercial intent
signals relevant to your offer."
Enter fullscreen mode Exit fullscreen mode

This used to require manually clicking through Meta's Audience Insights tool for each option. Now it's one prompt.


Verified Results: What Organisations Are Reporting

These are sourced from verified case studies and published reports — not projections.

Advolve (published on Anthropic's official customer page):

  • 90% reduction in operational work time from automating manual marketing tasks
  • 15% increase in customer ROAS across managed accounts

Agency example (published by Pipeboard):

  • A 3-person agency scaled from 8 to 20 client accounts without any new hires by using Claude for campaign audits and optimization workflows

E-commerce brand (published by Pipeboard):

  • Discovered $3,200/month being wasted on non-converting audiences
  • Identified and fixed in 10 minutes — a process that previously required a full audit

Industry benchmarks (from Marketing Agent research, 2026):

  • Marketers integrating AI into paid media workflows report an average 30% higher ROI
  • 27% improvement in campaign performance within six months of adoption

What Claude Cannot Do (Be Realistic)

This integration is powerful — but it's important to understand its limits.

Claude cannot:

  • Override Meta's ad policies or bypass platform restrictions
  • Guarantee ROAS improvements — it surfaces insights, but campaign success still depends on offer quality, landing pages, and product-market fit
  • Replace human judgment on brand strategy and creative direction
  • Access data from outside Meta's Marketing API (you'd need separate MCP servers for Google Ads, TikTok, etc.)
  • Take autonomous actions without your review unless you explicitly set up an agentic workflow

The correct mental model: Claude is an extremely capable analyst and operator who works at AI speed, but you're still the strategist. The best results come from teams who use Claude to handle the data-heavy operational work while humans focus on strategy, creative, and positioning.


Combining Meta Ads MCP with Other Servers

The real power compounds when you chain Meta Ads MCP with other data sources:

Workflow: Full-Funnel Attribution

Meta Ads MCP + Stripe MCP + PostgreSQL MCP
→ Claude sees ad spend, revenue generated, and customer LTV in one view
→ Calculates true blended ROAS accounting for subscription revenue, not just first-purchase
Enter fullscreen mode Exit fullscreen mode

Workflow: Creative Performance to Production

Meta Ads MCP + Slack MCP + Notion MCP
→ Claude detects underperforming creative
→ Posts alert to #paid-media Slack channel with specific data
→ Creates a Notion brief for the creative team with performance context
→ Total automation: 0 human hours
Enter fullscreen mode Exit fullscreen mode

Workflow: Weekly Reporting

Meta Ads MCP + Google Sheets MCP
→ Claude pulls 7-day performance data across all accounts
→ Formats it into your standard reporting template in Google Sheets
→ What used to take 3 hours now takes 4 minutes
Enter fullscreen mode Exit fullscreen mode

Getting Started Today

If you're a marketer (non-technical):

  1. Sign up for Pipeboard — 5-minute remote setup, $49/month
  2. Authorize your Meta Business Manager access
  3. Install Claude Desktop and add the MCP server config
  4. Start with the morning audit workflow above

If you're a developer:

  1. Clone pipeboard-co/meta-ads-mcp
  2. Generate your Meta Marketing API access token
  3. Run bash meta_ads_auth.sh to authenticate
  4. Add to your Claude Desktop config and test with get_ad_accounts

If you want to explore MCP first:
Go to MCP Playground Online and connect to any MCP server to see how the protocol works before setting anything up locally. You'll see the exact tools available and can run live requests in your browser.


The Bigger Picture

What's happening with Meta Ads and MCP is a preview of where all of paid media is heading.

The platforms have always had the data. The Marketing API has existed for years. But accessing that data required engineering resources, custom scripts, and dashboard tools that abstracted away the raw signal.

MCP removes that abstraction. It puts the data directly in the context window of a frontier AI model — with the ability to not just analyze it, but act on it. The feedback loop between performance data and campaign decisions, which used to take days, now takes seconds.

For individual marketers, this is a massive force multiplier. For agencies, it's the difference between managing 8 client accounts and managing 20. For in-house teams, it means the data analyst who used to spend Monday morning building the weekly report can now spend Monday morning doing something that actually requires human judgment.

The tools exist right now. The integration works. The results are verified. The only question is when you start.


The Meta Ads MCP server is an unofficial, community-built tool and is not affiliated with or endorsed by Meta Platforms, Inc. Always test integrations in a staging account before connecting to production ad budgets.


Resources:

Top comments (0)