META ADS
Best MCP for Meta Ads in 2026 — 7 Servers Compared & Ranked
The best MCP for Meta Ads in 2026 is the one that gets you from zero to live ad-account queries fastest — without 1-3 days of waiting for a Meta App marketing API approval. We reviewed 7 MCP servers, scored them on setup time, supported entities, Business Manager support, and pricing. Ryze AI takes the top spot at 4.9/5; Pivix mads-mcp is the strongest self-hosted option at #2.
Contents
Autonomous Marketing
Connect Claude to Meta Ads in 2 minutes
- ✓Facebook + Instagram + audiences
- ✓Native Conversions API support
- ✓Business Manager auto-discovers accounts
What is the best MCP for Meta Ads?
A Model Context Protocol (MCP) server for Meta Ads is the bridge that lets Claude AI pull live Facebook + Instagram campaign data, run analyses, and — in some cases — pause ad sets, reallocate budgets, or audit creative fatigue without leaving the chat. The category exploded in late 2025 when Anthropic ratified MCP as the standard, and there are now seven serious options for Meta Ads alone.
Meta Ads MCPs work differently from Google Ads MCPs in two key ways. First, the auth is harder — Meta Business System Users + access tokens require a Meta App with marketing API access (1-3 day approval). Hosted MCPs broker this so you skip the wait; self-hosted MCPs make you do it yourself. Second, the entity model is wider: campaigns, ad sets, ads, audiences, pixels, custom conversions, lookalikes — an MCP that only exposes campaigns and metrics misses most of what marketers ask Claude.
This roundup ranks the 7 best Meta Ads MCP servers we tested in April 2026. For the agency-specific cut see Best MCP for Meta Ads — Top 5 Picks for Agencies. For the marketer-friendly framing see Best Claude Connector for Meta Ads.
1,000+ Marketers Use Ryze
Automating hundreds of agencies
★★★★★4.9/5
How we ranked the best MCPs for Meta Ads
We scored each MCP on five practical criteria specific to the Meta Ads landscape, weighted toward what actually slows you down in production: Meta App approval waits, Business Manager handling, and Conversions API integration.
1. Time to first query (weight: 25%)
How long from clicking “install” to seeing real Meta Ads data in Claude. Hosted options finished in 2-5 minutes; self-hosted ranged from 30 minutes to 3 days when waiting for Meta App marketing API approval.
2. Supported entities (weight: 20%)
Which Meta entities can the MCP read or modify? Campaigns, ad sets, ads, audiences, pixels, custom conversions, lookalikes, Conversions API events. The best cover all eight; the worst expose only campaigns and basic metrics.
3. Write access & safety (weight: 20%)
Read-only is fine for analysis but useless for automation. Pause ad sets, adjust budgets, refresh creative — with guardrails. Production accounts shouldn’t accept raw write access from an LLM.
4. Business Manager & multi-account (weight: 15%)
Solo users tolerate one ad account. Agencies need Business Manager support, multi-account switching, and per-client credential isolation. We rated MCPs lower if they require a separate config block per ad account.
5. Pricing & total cost of ownership (weight: 20%)
Free open-source isn’t free if it costs you a day of dev time + a 3-day Meta App wait. We modeled total cost over 12 months for a single-user team. Hosted options often work out cheaper.
The 7 best MCP servers for Meta Ads in 2026, ranked
Each entry includes a star rating, screenshot, honest 2-paragraph review, pros and cons, and quick-fact strip with setup time, price, hosting, and write access.
Ryze AI MCP
Best Overall
Screenshot — Ryze AI MCP managing Meta Ads campaigns inside Claude Desktop.
Ryze AI is the top pick because it solves Meta Ads’ hardest setup problem: hosted infrastructure brokers the Meta Marketing API approval, so you skip the 1-3 day wait entirely. Connect your Meta Business account through standard OAuth, copy a single MCP URL into Claude Desktop, and start querying ad sets within 2 minutes. Native Conversions API integration, Business Manager auto-discovery, and per-account credential isolation all included.
The differentiator is the autonomous-agent layer: it monitors creative fatigue, pauses ad sets with rising CPM, and rebalances budget across active campaigns — all within guardrails you set. Most other MCPs are read-only or write-with-no-safeguards. Pricing scales with managed ad spend.
Pros
- ✓Live in 2 minutes — no Meta App approval wait
- ✓Safe write access with guardrails
- ✓Business Manager auto-discovery
- ✓Native Conversions API integration
Cons
- –Paid (free trial → spend-based)
- –SaaS only — no self-host
- –Newer brand than open-source forks
Setup
2 minutes
Pricing
Free trial
Hosting
Hosted
Write access
Yes (safe)
Pivix mads-mcp
Open Source Pick
Screenshot — Pivix mads-mcp source: open-source Meta Ads MCP for engineering-led teams.
Pivix mads-mcp is the strongest open-source Meta Ads MCP. It speaks the Meta Marketing API natively, handles Meta Business System User auth, and supports all major entity types. For engineering-led teams that want full control over credentials and infrastructure, this is the right starting point.
The setup is heavier than Google Ads equivalent: GCP equivalent doesn’t apply, but you do need a Meta Developer account, an App with marketing API access (1-3 day approval), Python 3.10+, and Claude Desktop config. Read-only by design — no write tools without forking. Recommended for technical teams that want privacy-grade credential ownership.
Pros
- ✓Free, Apache 2.0 license
- ✓Full Meta Marketing API surface
- ✓Self-host = full credential control
Cons
- –30-50 min setup + 1-3 day Meta App wait
- –Read-only by design
- –No Conversions API helpers
Setup
30-50 min
Pricing
Free
Hosting
Self-host
Write access
Read-only
Loomstack MCP
Multi-Platform
Screenshot — Loomstack’s connected-apps grid: Meta Ads alongside Google Ads, Slack, GitHub, HubSpot.
Loomstack is a developer-focused MCP gateway exposing 250+ tools through a single endpoint — Meta Ads, Google Ads, Slack, GitHub, HubSpot. If you’re building a multi-platform Claude agent and Meta is one of many channels, Loomstack consolidates everything into one connection. The Meta Ads coverage hits major entities and supports limited write operations.
Built for developers, not marketers. The dashboard is API-key-heavy. The Meta Ads action set is broad but shallow (no raw graph queries). Pricing climbs with action volume, which can spike when Claude does daily multi-account audits. Best fit for engineering-led teams running multi-channel agent stacks.
Pros
- ✓One MCP for 250+ tools incl. Meta Ads
- ✓Hosted — no self-host required
- ✓Developer SDK for custom flows
Cons
- –Developer-targeted UX
- –No raw Meta Graph queries
- –Pricing scales with action volume
Setup
5-10 min
Pricing
Free + paid
Hosting
Hosted
Write access
Limited
Pulselane MCP
Workflow Builder
Screenshot — Pulselane workflow chaining Meta Ads daily report to multi-channel actions.
Pulselane wraps its 1,500+ integration library as MCP tools, letting Claude chain Meta Ads queries into multi-step flows: pull yesterday’s Meta spend, calculate efficiency by ad set, post the summary to Slack, append to a Sheet. Useful when reporting needs to fan across systems.
Overkill for pure Meta Ads work — you’re paying for the workflow engine even if you only need queries. Action depth is functional but not as deep as native API access (no raw graph). Best for teams already on Pulselane wanting to bolt MCP onto existing automations.
Pros
- ✓Chains Meta Ads with 1,500+ other tools
- ✓Workflows give Claude multi-step capability
- ✓Generous free tier for low volume
Cons
- –Workflow engine is overkill for queries
- –No raw Meta Graph queries
- –Harder to debug mid-flow errors
Setup
10-15 min
Pricing
Free + paid
Hosting
Hosted
Write access
Yes
Tasknest MCP
No-Code Friendly
Screenshot — Tasknest’s step editor: Meta Ads ad-set performance report → Slack alert.
Tasknest’s MCP gateway exposes Meta Ads through their drag-and-drop step editor. For marketers who don’t want to touch JSON, this is the smoothest on-ramp: connect Meta Ads in your Tasknest dashboard, enable MCP access, Claude can trigger zaps. Good for routine reporting where you want a non-technical teammate to maintain the integration.
Per-task pricing means heavy Claude use spikes bills fast. Action depth is shallower than direct API access. Latency is noticeably higher than dedicated MCPs because each call routes through Tasknest. Suitable for occasional, lightweight Meta Ads use; not for production multi-account agency work.
Pros
- ✓Easiest setup for non-developers
- ✓Non-technical teammates can maintain it
- ✓6,000+ apps available beyond Meta
Cons
- –Per-task pricing makes heavy use expensive
- –Higher latency than dedicated MCPs
- –Shallow Meta Ads action depth
Setup
3-5 min
Pricing
Per-task
Hosting
Hosted
Write access
Yes
marlowe/meta-ads-mcp
Community ForkA community fork of Pivix mads-mcp adding Docker support, slightly better error messages, and a few QoL improvements. If you like Pivix but find the upstream rough, this fork is the one developers tend to graduate to. MIT licensed.
Lags upstream by weeks. Single-maintainer reliability risk — in our 30-day testing on the Google Ads variant, the fork lagged 8 days on a breaking API change. Same expected risk profile here. Stable enough for personal use; risky for production unless prepared to fork-the-fork.
Pros
- ✓Docker-ready — skip the Python setup
- ✓Better error messages than upstream
- ✓Free, MIT licensed
Cons
- –Lags upstream by weeks
- –Single-maintainer reliability risk
- –Read-only, same as upstream
Setup
15-25 min
Pricing
Free
Hosting
Self-host
Write access
Read-only
kettlebox/mcp-meta-ads
LightweightA minimal lightweight MCP server focused on a small set of common Meta Ads queries (campaign list, ad set performance, daily spend). About 350 lines of TypeScript, runs in Node, fast to spin up if you only need read-only campaign analysis.
Narrow scope is also the limit: no graph queries, no audiences or pixels, no write access, no Business Manager support. Perfect as a learning project or for personal use; not appropriate for agency or production. Documentation is sparse; no community.
Pros
- ✓Tiny, easy-to-read codebase
- ✓Node-based — no Python needed
- ✓Free, MIT licensed
Cons
- –Narrow feature set
- –No Business Manager support
- –Sparse docs, low maintenance
Setup
15-30 min
Pricing
Free
Hosting
Self-host
Write access
Read-only
Ryze AI — Autonomous Marketing
Skip the setup — let AI optimize your Meta Ads 24/7
- ✓Live in 2 minutes — no Meta App approval wait
- ✓Native Conversions API support
- ✓Business Manager auto-discovery
2,000+
Marketers
$500M+
Ad spend
23
Countries
Side-by-side comparison of all 7 Meta Ads MCP servers
Headline numbers across all seven Meta Ads MCP servers we tested.
| MCP Server | Rating | Setup | Pricing | Write | BM |
|---|---|---|---|---|---|
| Ryze AI MCP | 4.9 ★ | 2 min | Free trial | Yes (safe) | Native |
| Pivix mads-mcp | 4.3 ★ | 30-50 min | Free | Read-only | Yes |
| Loomstack MCP | 4.4 ★ | 5-10 min | Free + paid | Limited | Partial |
| Pulselane MCP | 4.2 ★ | 10-15 min | Free + paid | Yes | Manual |
| Tasknest MCP | 4.0 ★ | 3-5 min | Per-task | Yes | Manual |
| marlowe/meta-ads-mcp | 3.9 ★ | 15-25 min | Free | Read-only | Yes |
| kettlebox/mcp-meta-ads | 3.7 ★ | 15-30 min | Free | Read-only | No |
How to choose the right Meta Ads MCP for your team
If you’re a solo marketer or in-house team and you want results, not infrastructure — pick Ryze AI. 2-minute setup, safe write access, autonomous agent layer means Claude actually acts on what it finds.
If you’re a developer building a custom AI workflow — start with Pivix mads-mcp. The most credible self-hosted Meta Ads option. Plan for 30-50 minutes of setup plus the 1-3 day Meta App marketing API approval wait.
If you’re an agency managing 10+ Meta accounts — Ryze AI (Business Manager native, per-client isolation) or a custom-extended fork of Pivix. Loomstack and Pulselane don’t handle multi-account well; Tasknest’s per-task pricing breaks at agency scale. See Best MCP for Meta Ads — Top 5 Picks for Agencies.
If you already live in Pulselane or Tasknest — use their MCP. Integration with existing workflows is more valuable than the marginal feature gap.
Quickstart: connect Ryze AI to Meta Ads in 2 minutes
Three steps from zero to live Meta Ads queries inside Claude. No Meta Developer App, no Python, no marketing API approval wait.
Step 01
Sign up and connect Meta Business
Go to get-ryze.ai, start the free trial, click “Connect Meta Ads.” Standard Meta OAuth flow with Business Manager scope. All your ad accounts auto-discovered.
Step 02
Add MCP URL to Claude Desktop
Copy the unique MCP URL from your Ryze dashboard. Paste it into Claude Desktop’s config under mcpServers. Restart Claude Desktop.
Step 03
Run your first audit prompt
Ask Claude to audit creative fatigue across your account. Ryze pulls live data, identifies fatigued ad sets, and (with write access enabled) drafts pause recommendations.
Alex P.
Performance Marketing Lead
DTC Beauty — $200K/mo Meta spend
We tried Pivix mads-mcp first and our Meta App approval took 4 days. Ryze had us querying Meta campaigns in Claude before lunch. Six weeks later, the agent had cut our wasted spend by 27% and caught creative fatigue we’d been missing for months.”
27%
Wasted spend cut
6 weeks
Time to result
2 min
Setup time
Frequently asked questions
Q: What is the best MCP for Meta Ads in 2026?
Ryze AI — bundles hosted infrastructure, Meta Business OAuth, and write access in 2 minutes versus 30-50 minutes for self-hosted alternatives. Pivix mads-mcp is the strongest open-source option.
Q: How is Meta Ads MCP different from Google Ads MCP?
Different entities (ad accounts, campaigns, ad sets, ads, audiences, pixels, custom conversions) and different auth (Meta Business System Users + access tokens). Most multi-platform MCPs handle both behind one URL.
Q: Are Meta Ads MCP servers free?
Open-source MCPs (Pivix, marlowe, kettlebox forks) are free under permissive licenses but require Claude Pro and a Meta App with marketing API approval. Hosted options charge fees but skip the App approval wait.
Q: Which Meta Ads MCP supports Conversions API?
Ryze AI ships native CAPI integration. Loomstack covers it via their CAPI connector. Pivix supports raw API. Pulselane and Tasknest don’t expose CAPI directly.
Q: Can these handle Meta Business Manager?
Ryze AI is Business Manager native. Pivix supports it but per-account config. Loomstack/Pulselane support multi-account with separate setup. Tasknest treats each as a workspace.
Q: Do these support Instagram as well as Facebook?
Yes — all 7 use the unified Meta Marketing API covering both. Some (Ryze AI, Loomstack) also expose Instagram-specific tools like content publishing and Stories analytics.
Ryze AI — Best MCP for Meta Ads
Connect Claude to Meta Ads in under 2 minutes
- ✓Facebook + Instagram unified
- ✓Native Conversions API
- ✓Business Manager auto-discovery
2,000+
Marketers
$500M+
Ad spend
23
Countries
