Run Meta Catalog Ads from Claude Code

Manage Meta Catalog Ads (Advantage+ Catalog / DPA) campaigns inside Claude Code (CLI) — 16 tools, OAuth setup in about 60 seconds, no dashboard switching.

Try free View Meta Catalog Ads docs

16 Meta Catalog Ads tools, all in Claude Code
Paused-by-default. Cannot delete campaigns.
OAuth setup in ~2 minutes

See it in action

In Claude Code

›List my Meta product catalogs and check whether my catalog is ready for retargeting. If it is, create an Advantage+ Catalog retargeting campaign for my "Best Sellers" product set at $40/day, targeting people who viewed or added to cart in the last 14 days. Leave it paused so I can review before launch.

Check catalog readiness, then launch retargeting DPA — Readiness check, then a paused retargeting DPA campaign built from your product feed.

Overview

Adspirer is the MCP server that connects Claude Code (CLI) to your Meta Catalog Ads ad accounts, turning campaign management into a chat conversation. Anthropic Claude Code in your terminal — perfect for engineering teams that script ad ops. On the platform side, 16 tools cover dynamic product ads that pull each SKU's image, name, and price straight from your Meta catalog to run prospecting and retargeting across the whole feed — no ad-per-product by hand. Adspirer reads and writes — pull performance reports, audit connect a commerce manager catalog, launch new campaigns, pause underperformers, and reallocate budget — all from chat. New campaigns are always created paused so you can review before they go live, Adspirer cannot delete existing campaigns by design, and the free tier (15 tool calls / month, no credit card) is enough to run a full audit before you pay. Setup takes about 60 seconds via one CLI command.

Safety guarantees

New campaigns always created paused for review
Adspirer cannot delete existing campaigns
Budget changes need explicit confirmation
OAuth 2.1 + PKCE — passwords never seen

How it works

Claude Code

You ask in chat

prompt

Adspirer

16 tools, paused-by-default

tool calls

Meta Catalog Ads

Live data, paused for review

Step 01

Connect

Paste the MCP URL into Claude Code, OAuth into Meta Catalog Ads.

Step 02

Manage

Ask in chat. Adspirer routes through 16 Meta Catalog Ads tools.

Step 03

Scale

Switch accounts in chat. Same audits across every client.

What you can do

16 tools across Meta Catalog Ads. The ones you'll use most:

Connect a Commerce Manager catalog — `list_meta_catalogs` lists every product catalog attached to your ad account — the ones you built in **Meta Commerce Manager** or synced from your store platform. Adspirer manages the **ads** on top of the catalog; it does not create or edit the product feed itself.
Browse the products in a catalog — `list_meta_products` walks the products inside a catalog so you can see exactly what Meta will render — image, name, price, and availability pulled straight from the feed — before you spend a dollar.
Build targetable product sets — `list_meta_product_sets` shows existing subsets and `create_meta_product_set` cuts a new one with filter rules like "best sellers under $50" — so you advertise a curated slice of the catalog, not the whole feed.
Launch DPA for prospecting + retargeting — `create_meta_catalog_campaign` launches an Advantage+ Catalog campaign — **prospecting** (show relevant products to cold audiences) or **retargeting** (re-show the exact SKUs a visitor viewed or added to cart). `validate_catalog_readiness` first checks your pixel data can support retargeting. Every catalog campaign is created **PAUSED** for review.
Compare product-set performance — `compare_meta_catalog_product_sets` ranks your product sets head-to-head, `get_meta_product_performance` breaks spend, sales, and ROAS down per SKU, and `detect_meta_catalog_waste` flags products burning budget with no return — so you scale winners and prune losers.
Works with Shopify & WooCommerce catalogs — Already sync your store to Meta Commerce Manager from **Shopify**, **WooCommerce**, or another platform? Adspirer reads that catalog as-is via `list_meta_catalogs` and runs ads on it — no re-import. Set the feed up once in your store, then create, target, and optimize the DPA campaigns from chat. Adspirer manages the ads, not the feed.

Campaign types

Every Meta Catalog Ads format Adspirer supports — request one in chat.

Advantage+ Catalog / DPA

Dynamic product ads that pull image, name, and price straight from your catalog — Meta renders the ad per shopper. `create_meta_catalog_campaign` launches it, created PAUSED.

Prospecting DPA

Show relevant products from your feed to cold audiences who have not visited yet — Meta matches SKUs to shopper intent. No pixel history required.

Retargeting DPA

Re-show the exact products a visitor viewed or added to cart within your retargeting window. Needs view / add-to-cart / purchase pixel events — `validate_catalog_readiness` confirms you have them.

Product sets

Advertise a curated slice of the catalog — "best sellers under $50", one collection, one brand. `create_meta_product_set` defines the filter; `add_meta_catalog_ad` points an ad at it.

Pick an intent

More prompts to try

Claude Code shines on multi-step agent tasks — drop a brief, walk away, get a report.

Per-SKU performance & wasted spend — Per-product ROAS breakdown plus a wasted-spend list to prune.

Per-SKU performance & wasted spend

Analyze my Meta catalog performance for the last 30 days. Which products have the best ROAS, and which SKUs are burning budget with no sales? Show me a per-product breakdown and recommend which products to pause.

Pick your audience

Who this is for

In-house growth marketer running Meta Catalog Ads solo

Each Monday, ask Claude Code to pull last week's Meta Catalog Ads performance, surface campaigns running below your ROAS threshold, and recommend creative refreshes for fatigued ads.

Replaces a 60–90 minute manual review with a 5-minute chat, and surfaces problems before they tank ad-set performance.

Compare & decide

Compare

Adspirer vs alternatives

For running Meta Catalog Ads from Claude Code.

	Adspirer	DIY MCP server	Legacy SaaS dashboard
Setup time	~60 seconds via one CLI command	2–4 hours building MCP server	30–60 min onboarding + sales call
Cost — entry tier	Free (15 calls / mo)	Hosting + maintenance	$200–500 / mo minimum
Works inside Claude Code	Yes — one CLI command	Yes (if you build it correctly)	No — external dashboard only
Multi-account	Yes — switch in chat	Manual per-account auth	Yes — but each account billed
Read + Write	Full read + write (create / pause / update)	Whatever you build	Mostly read-only or seat-gated writes
Safety: cannot delete	Hard-coded — no delete tool	Up to you	Varies
Pricing transparency	Public — $0 / $49 / $99 / $199	Self-hosted	Often quote-only

Cost

Pricing

If Adspirer wins for you, here's what it costs. Start free; upgrade if you outgrow it.

Free Forever

15 tool calls / mo

All platforms. ChatGPT & Claude access. No credit card.

Start free →

Best for Claude Code

Plus

$49 / mo

150 tool calls / mo

Performance analysis + standard campaigns.

Compare Plus →

Pro

$99 / mo

600 tool calls / mo

AI optimization, bulk ops, deeper diagnostics.

Compare Pro →

Max

$199 / mo

3,000 tool calls / mo

Priority support (24h SLA), custom integrations.

Compare Max →

Set up

Configure

Required: Claude API access (or Claude.ai Pro / Max). Most users finish in about two minutes.

Show setup steps for Claude Code

Add Adspirer to Claude Code

Run in your terminal:

claude mcp add --transport http adspirer https://mcp.adspirer.com/mcp

Authenticate

Claude Code launches your browser for OAuth. Sign in to Adspirer and link your ad accounts.

Verify

Run claude and ask: Check my connected ad platforms. Tools should now appear in the available-tools list.

Common questions

FAQ

Setup

Do I need a developer to set this up?

Some terminal comfort helps but you don't need to be a developer — adding the MCP server is one command (claude mcp add --transport http adspirer https://mcp.adspirer.com/mcp or the equivalent for your CLI). OAuth happens in your browser. Total time: about 60 seconds.

Do I need a pixel or catalog events to run DPA?

Prospecting works without pixel history. Retargeting needs recent view / add-to-cart / purchase events so Meta knows which products to re-show whom. Run validate_catalog_readiness first — it pre-flights your catalog plus pixel data and tells you whether you can retarget or only prospect, *before* you spend.

Capabilities

Can I switch from Claude Code to a different AI client later?

Yes. Your Adspirer account is independent of the AI client — sign up once, then connect the same MCP URL from ChatGPT, Claude, Cursor, Codex, Windsurf, or any supported client. Tool calls are pooled across clients on the same plan; switching costs you nothing.

What is a catalog and where does it come from?

A catalog is your product feed — every SKU with its image, name, price, and availability. You build it once in Meta Commerce Manager, or sync it automatically from Shopify, WooCommerce, or another store platform. Adspirer reads whatever catalog is attached to your ad account via list_meta_catalogs and manages the ads on top of it — it does not create or edit the product feed itself.

What's the difference between prospecting and retargeting DPA?

Prospecting shows relevant products from your feed to cold audiences who have not visited your site — Meta matches SKUs to shopper intent, no pixel history required. Retargeting re-shows the exact products someone viewed or added to cart within a set window. create_meta_catalog_campaign runs either mode; retargeting depends on recent pixel events (see below).

Compare

What's the read vs. write boundary on Meta Catalog Ads?

Adspirer is full read and write. It can pull reports, audit performance, and analyze data (read), and it can launch new campaigns, pause underperformers, update budgets, and adjust targeting (write). Two safety guardrails are hard-coded: new campaigns are always created paused so you review before they go live, and Adspirer cannot delete existing campaigns. You keep full control.

What are product sets and why use them?

A product set is a targetable subset of your catalog — "best sellers under $50", one collection, or one brand. create_meta_product_set cuts one with filter rules, list_meta_product_sets shows the sets you already have, and compare_meta_catalog_product_sets ranks them — so you spend on the sets that actually convert instead of blasting the whole feed.

Why run DPA instead of building an ad for every SKU by hand?

With hundreds or thousands of SKUs — and prices and stock changing daily — hand-building an ad per product is impossible to maintain. Dynamic product ads pull each product's image, name, and price straight from the catalog and render the ad automatically, so prospecting and retargeting scale across the entire feed with one campaign. get_meta_product_performance and detect_meta_catalog_waste then let you optimize at the per-SKU level.