Run your ads from Claude.

What this actually is

Claude supports custom connectors, which is Anthropic's name for remote MCP servers. Muze is a paid media MCP server. Adding it hands Claude 149 tools split across Meta Ads at 37, Google Ads at 41, Amazon Ads at 48, Shopify at 15, and 8 cross-platform tools that work across all of them.

That last group is the interesting one. get_blended_performance returns total ad spend across Meta, Google and Amazon against Shopify revenue in a single call, with blended MER and ROAS already computed. It is a cheap, non-model read, which means Claude can call it repeatedly while reasoning without turning your account into a bill. Most of the good analysis sessions start there and drill down.

Why people put the ad account in Claude first

Claude is patient with messy, multi-step reasoning, and account diagnosis is exactly that. The question is never “what was ROAS.” It is “ROAS fell 30 percent, which of the eleven things that could cause that actually did.” That means reading spend, then ad set delivery, then creative fatigue, then whether Shopify revenue moved at all, and holding the whole thing in mind while you do.

It also handles being told it is wrong. An assistant that reads an account and then reconsiders when you point out that a campaign was paused mid-week is more useful than one that produces a confident wrong summary in a nicer format. Read-only integrations are safe because they are useless: the value shows up when the analysis ends in a specific action you can approve.

How connecting works

You need a Muze account with at least one connected ad or commerce account. Everything is OAuth. Muze never asks for your platform passwords, and Claude never handles a credential.

1. Create a Muze account and authorize your accounts. Sign up for Muze and authorize Meta Ads, Google Ads, Amazon Ads or Shopify over OAuth. Pick only the accounts you want reachable. You can revoke any of them later without touching the connector.
2. Open Settings and go to Connectors. In Claude, open Settings and find the Connectors section, then choose Add custom connector.
3. Enter the Muze MCP URL. Enter https://backend.muzecmo.com/mcp as the connector URL and save it.
4. Complete the Muze OAuth flow and start a new conversation. Sign in with Muze when the authorization window opens and approve the connection. Start a new conversation, then ask Claude to list your connected ad accounts. It should call get_my_accounts and name them back to you.

Connector availability varies by Claude plan. Desktop and developer clients can connect to the same endpoint using a Muze API key instead: see the connection guide.

The connection guide carries current per-client configuration detail.

What you can ask once it is connected

Claude rewards specificity about the shape of the answer you want. Tell it what to rank by, what window to use, and whether you want it to stop at the diagnosis or prepare the fix.

• Audit Meta, Google and Amazon for the last 7 days and rank the issues by wasted spend. get_meta_performance, get_google_performance and get_amazon_performance, cross-checked against get_blended_performance.
• Compare this month to last month on Meta and explain what actually changed. compare_meta_performance, with get_ad_insights for the ads that moved.
• Is my Shopping feed healthy, and are the disapprovals costing me anything? get_merchant_feed_health plus list_merchant_center_products.
• Which products are actually driving revenue, and are we advertising them? get_top_products and get_shopify_orders, checked against list_account_ads.
• Pause every Meta ad set below 1.0 ROAS over the last 14 days, but show me the list first. pause_ad_set, which previews the exact set of ad sets and waits for confirmation.

Those are real tool names, not illustrations.

Nothing spends until you say so

An agent that only reports is a nicer spreadsheet, so Muze can act. The gate in front of it is what makes that safe.

• Every write previews first. You see exactly what will change, and it waits for your confirmation.
• New campaigns are created paused. Creating one cannot start spending.
• Access is scoped to the accounts you authorize over OAuth, and you can revoke it.
• Muze never takes a percentage of your spend. You pay for software, and your budget stays yours.

Claude asks for permission before running a tool, and Muze asks again before any write executes. An assistant that misreads one prompt should cost you a click, not a weekend of budget.

Where Claude is the wrong client

Custom connectors are not on every Claude plan, and in a team workspace an admin may have to enable them. That is an Anthropic setting and Muze cannot change it.

Connectors are also per conversation in practice: a long thread that has drifted into other topics uses its tools less reliably than a fresh one aimed at the account. Start a new conversation for a new audit. And Claude is a chat, not a scheduler. If you want the same weekly check to run without you, a terminal client is the closer fit.

One connection, four platforms

Authorize Meta Ads, Google Ads, Amazon Ads and Shopify once and all four are reachable from the same conversation. Single-platform integrations cannot answer the questions that matter: whether Meta is taking credit for Google's conversions, what blended MER actually is against real store revenue, or where the wasted spend is when you look at everything at once.

Platform detail: Meta Ads, Google Ads, Amazon Ads, Shopify. The Muze MCP overview has the tool inventory, pricing has the plans, and every supported client is listed in one place.

Frequently asked questions

How do I connect Muze to Claude?

Open Claude's Settings, go to Connectors, choose Add custom connector, enter https://backend.muzecmo.com/mcp, and complete the Muze OAuth sign-in. Then start a new conversation. Nothing to install.

Does this work in Claude Desktop as well as claude.ai?

Yes. Hosted Claude uses OAuth against the same endpoint. Desktop and developer clients connect to that endpoint using a Muze API key from your Muze API Access page, sent as a header. Both routes reach the same 149 tools.

Can Claude create and launch campaigns?

Yes, on a paid Muze plan. It can build Meta campaigns, Google Search, Shopping, PMax, Demand Gen and Video campaigns, and Amazon auto and manual campaigns. Every build returns as a preview for your approval and is created paused, so nothing begins delivering on its own.

What does Claude cost on top of Muze?

Nothing extra from us. You bring your own AI, so Muze never charges you for model tokens. You pay Anthropic for Claude and Muze for the connector, and Muze takes no percentage of your ad spend.

Is Shopify write access included?

Shopify is almost entirely read-only in the MCP: 13 of its 15 tools are reads: orders, revenue, products, feed and sync status. Write tools exist for Meta Ads, Google Ads and Amazon Ads only. Your store data is used for context and measurement, not modified.

Can I limit which accounts Claude can reach?

Yes. Access is scoped to the accounts you authorize in Muze. Connect one ad account or twenty, and revoke any of them later. The connector only ever sees what you granted.

Muze in other AI clients