Best Claude Connector for Meta Ads (2026 Guide)

Screenshot — Ryze AI Claude connector running a live Meta Ads audit, no developer involvement.

Ryze AI is the cleanest Claude connector for Meta Ads if you don’t want to write code, register a Meta Developer App, or wait for marketing API approval. The whole setup is point-and-click in a web dashboard: connect your Meta Business account through standard OAuth, copy the unique MCP URL, paste it into Claude Desktop’s config, restart Claude. Done. From there you can ask Claude any question about your account — “which ad sets are creative-fatigued?”, “why did Reels CPM spike on Tuesday?”, “draft a fresh hook based on my top-performing ad” — and get answers from your real Facebook + Instagram data. We break this down further in our Google keyword tool API guide.

The big differentiator for marketers: optional write access. With one toggle, Claude can pause fatigued ad sets, refresh creative, or rebalance budget on your behalf, within safety limits you set (max change per day, dry-run mode, per-ad-set frequency caps). Most other connectors are read-only or write-with-no-safeguards. Pricing scales with managed Meta ad spend, so a single account at $50K/mo is dramatically cheaper than enterprise alternatives.

ScaleForge is a solo developer project with one of the cleanest install stories of any open-source Meta connector. The Smithery path is the fastest: npx -y @smithery/cli install @getscaleforge/mcp-meta-ads and Claude Desktop picks it up automatically. It also installs via standard npm and is listed on both Smithery and Glama. The 32 tools cover 10 categories — campaigns, ad sets, creatives, media uploads, insights, bulk operations, Pages, and ad library searches — against Meta Graph API v24.0.

Like all self-hosted options here, you still need your own Meta access token and a Meta Developer App with marketing API access. The 1-3 day approval wait applies. The upside is the package is MIT-licensed and fully inspectable, and the Smithery one-click install is the most beginner-friendly path among the local stdio connectors. Best for a developer who wants to get Claude connected quickly without setting up Python, or who needs a package compatible with Claude Desktop, ChatGPT, and Cursor interchangeably.

attainmentlabs meta-ads-manager-mcp is the smallest and most focused option in this roundup: 13 explicitly named tools that cover the essential Meta Ads lifecycle and nothing else. Install is a single command — pip install meta-ads-manager-mcp or uvx meta-ads-manager-mcp — and the package is live on PyPI at v0.2.0. The tools cover campaign creation, listing ad sets and ads, status checks, insights, image upload, daily budget updates, bulk status changes, and campaign pause/activate/delete.

For a developer who wants to understand exactly what Claude can and can’t touch before granting broad write access, this narrow 13-tool surface is an advantage: there are no surprises, the scope is clear, and the code is small enough to audit in an afternoon. It requires a Meta Developer App and the 1-3 day marketing API approval just like every self-hosted option. There’s no Smithery listing and no hosted endpoint — pure PyPI, pure local stdio.

hashcott’s meta-ads-mcp-server has the most thoughtful read/write safety design of any open-source option in this list. The 35 read-only tools are always active — Claude can audit everything. The 19 write tools are explicitly opt-in, meaning you consciously enable mutations per Claude session rather than having write access always live. For a developer who wants to let Claude act on Meta data but is cautious about unintended changes, this explicit split is a meaningful feature.

Install is clean: npx meta-ads-mcp-server --access-token YOUR_TOKEN with no separate install step. It has gone through 9 npm versions, which signals active maintenance. The caveats are the same as most self-hosted options: you still need a Meta Developer App and the associated 1-3 day marketing API approval per ad account, and there’s no dashboard or UX — it’s a developer tool.

If raw Meta API surface area matters to you, mikusnuz’s @mikusnuz/meta-ads-mcp is the most comprehensive open-source option: 135 tools against Meta Marketing API v25.0, covering campaigns, ad sets, ads, audiences, creatives, insights, and catalogs. That’s more than four times the coverage of attainmentlabs’ 13-tool server. It ships on npm, runs via npx -y @mikusnuz/meta-ads-mcp with no separate install, and has 60 GitHub stars and 11 forks as of the time of writing.

The tradeoff is that sheer tool count doesn’t equal ease of use. This is a developer tool: you supply your own Meta access token, manage your own Meta Developer App approval, and direct all Claude actions yourself via prompt. There is no hosted endpoint, no autonomous optimization, and no dashboard. For a developer who needs to expose the full Meta Marketing API to Claude and doesn’t want to write the integration themselves, this is the fastest path to 100% coverage.