Which platforms does Muze MCP cover?

Meta Ads, Google Ads, Amazon Ads and Shopify, through one OAuth connection. The wider Muze platform also covers TikTok Ads and Bing Ads, but those are not reachable through the MCP.

No. It has 149 tools and most of the Meta and Amazon surface is writes: creating campaigns, changing budgets, adjusting bids, adding negative keywords, pausing ads. Every write returns a preview and waits for explicit confirmation, and new campaigns are created paused.

How is this different from using each platform’s own dashboard?

The useful questions are cross-platform. Blended ROAS against real store revenue, whether Meta is taking credit for what Google started, where the wasted spend is across all of it. You cannot answer any of those from inside one channel, which is why Muze reads all four in the same session.

The free tier includes 25 read-only tool calls per month across all connected platforms. Write actions require a paid plan. Muze never takes a percentage of ad spend, and never holds or intermediates ad budget.

Do I need a developer to connect it?

No. Connection is OAuth with your normal platform logins. There is no Meta developer app to register, no Google Ads developer token to apply for and no Amazon Advertising API application to file.

Muze solutions: DTC brands, agencies, Shopify, Amazon, technical teams

In short

Muze connects Meta Ads, Google Ads, Amazon Ads and Shopify to ChatGPT, Claude or any MCP client through a single OAuth connection, then reads and acts on those accounts in conversation. These six pages describe what that changes for a specific kind of advertiser: DTC brands arguing with attribution, agencies buried in weekly reporting, Shopify stores measuring against real orders, Amazon sellers stuck in a separate tool, technical teams evaluating the protocol, and solo founders with no media buyer. Every write previews first, and campaigns are created paused.

Pick your Monday

DTC brandsBlended ROAS against real store revenue, when Meta and Google both claim the same order.Ecommerce agenciesWeekly reporting, new-client audits, and a preview you can show the client before the budget moves.Shopify storesAd spend measured against orders that exist, down to which product actually sold.Amazon sellersSearch terms, negatives, bids and TACoS, in the same place as your Meta and Google spend.Technical teamsThe protocol, the endpoint, the 149-tool surface, scoped OAuth and how writes are gated.Solo foundersThe weekly account work, done in one conversation, with a confirmation step before anything spends.

What every one of them has in common

One OAuth connection covers Meta Ads, Google Ads, Amazon Ads and Shopify. There is no developer account to register, no API token to mint and no platform password to hand over. Inside ChatGPT, Claude or any MCP client, Muze has 149 tools: Core and cross-platform 8, Meta Ads 37, Google Ads 41, Amazon Ads 48 and Shopify 15.

The write coverage is the point. Read-only integrations are safe because they are useless, and the valuable work is acting: pausing the loser, moving the budget, adding the negatives, building the campaign. So the safety model has to be structural rather than a promise. Every write returns a preview and waits for explicit confirmation. New campaigns are created paused, forced by the API rather than requested in a prompt. Tools that stop live spend require an explicit confirmation flag. And Muze never takes a percentage of ad spend, because a tool that earns more when you spend more is not on your side of the table.

Why segment pages instead of one page

Because the problems genuinely differ. A DTC brand needs blended ROAS because Meta and Google are both claiming the same order. An agency needs an approval trail before it touches a client budget. A Shopify operator needs product-level truth rather than platform-attributed revenue. An Amazon seller needs search terms, negatives and TACoS, in the same place as everything else instead of a separate tool. A technical team needs the protocol, the tool surface and the auth model. A solo founder needs the weekly work done without a media buyer.

Same connection underneath. Read how Muze MCP works for the mechanics, or the full tool reference if you would rather read the surface than a description of it.

Frequently asked questions

Which platforms does Muze MCP cover?: Meta Ads, Google Ads, Amazon Ads and Shopify, through one OAuth connection. The wider Muze platform also covers TikTok Ads and Bing Ads, but those are not reachable through the MCP.
Is Muze read-only?: No. It has 149 tools and most of the Meta and Amazon surface is writes: creating campaigns, changing budgets, adjusting bids, adding negative keywords, pausing ads. Every write returns a preview and waits for explicit confirmation, and new campaigns are created paused.
How is this different from using each platform’s own dashboard?: The useful questions are cross-platform. Blended ROAS against real store revenue, whether Meta is taking credit for what Google started, where the wasted spend is across all of it. You cannot answer any of those from inside one channel, which is why Muze reads all four in the same session.
What does it cost?: The free tier includes 25 read-only tool calls per month across all connected platforms. Write actions require a paid plan. Muze never takes a percentage of ad spend, and never holds or intermediates ad budget.
Do I need a developer to connect it?: No. Connection is OAuth with your normal platform logins. There is no Meta developer app to register, no Google Ads developer token to apply for and no Amazon Advertising API application to file.

Connect it and ask one hard question

OAuth, read-only to start, 25 free tool calls a month. Ask what last month actually returned across every platform and see whether you believe the answer.

Start free