Run your ads from the AI you already use.

Pick your client

The dashboard is the problem, not the interface

Ad platforms made their money by making you live inside their UI. Most AI advertising tools answer that by building a fifth dashboard, which is the same problem with better typography. Muze does not have a place for you to log into every morning. It attaches to the tool you are already thinking in, and the ad account becomes something you ask about rather than somewhere you go.

That choice has a cost worth stating. If you want a wall of charts to show a client, a chat client is not it. What you get instead is the answer to the question you actually had, drawn from four platforms at once, in the window you were already in. For most operators that trade is worth making on a Tuesday afternoon and not worth making the day the quarterly report is due.

How connecting works

The connection belongs to your Muze account, not to any one client. Authorize your accounts once, then add Muze wherever you want to use it.

1. Authorize your accounts in Muze. Create a Muze account and connect Meta Ads, Google Ads, Amazon Ads or Shopify over OAuth. There is no developer application to file, no API token to mint on the platform side, and Muze never receives your platform passwords.
2. Add Muze to the AI client you already use. Hosted clients such as ChatGPT and Claude add Muze as a custom connector pointed at https://backend.muzecmo.com/mcp. Desktop and developer clients point at the same endpoint and authenticate with a Muze API key from the Muze API Access page.
3. Ask, review, approve. Ask your first question in plain English. Reads return straight away. Every write returns a preview of exactly what will change and waits for your explicit confirmation, and new campaigns are created paused.

Hosted clients handle this with OAuth and a connector URL. Desktop and developer clients use a Muze API key instead, created on the API Access page in the Muze app. Both routes reach the same endpoint and the same tools. The connection guide carries the current per-client detail.

What changes between clients, and what does not

What does not change: the tool inventory. All 149 tools are available everywhere, split 8 cross-platform, 37 Meta Ads, 41 Google Ads, 48 Amazon Ads and 15 read-only Shopify. The permission model does not change either. A write preview in a terminal behaves exactly like a write preview in a browser tab.

What does change: the setup path, the presentation, and who in your company will realistically use it. Hosted chat clients are the shortest route for anyone who does not want to open a config file. Editor and terminal clients are better for repeating the same audit across many accounts, and they show you the tool call and its arguments before it runs. A Slack agent puts the approval where your team can see it. Same capability, different door.

Nothing spends until you say so

Read-only integrations are safe because they are useless. The valuable part is acting: building the campaign, pausing the loser, moving the budget. That is also where the risk is, which is why the gate in front of it matters more than the tool count.

• 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.

What sits behind the connection

Four platforms, one authorization. Meta Ads and Google Ads cover the campaign work most people arrive for, Amazon Ads is the one most ad MCP servers skip, and Shopify supplies the revenue that turns spend into a ratio worth looking at. The Muze MCP overview explains how the pieces fit, and pricing is a flat monthly subscription rather than a share of your budget.

Frequently asked questions

Which AI clients does Muze work with?

ChatGPT, Claude, Cursor, Claude Code, Codex, and any other client that supports MCP, including AI agents running inside Slack. Muze is a remote MCP server, so support depends on whether your client can connect to one, not on whether we built a specific integration for it.

Does the tool set change between clients?

No. All 149 tools are available in every client: 8 cross-platform, 37 for Meta Ads, 41 for Google Ads, 48 for Amazon Ads and 15 Shopify tools, 13 of them read-only. What differs is the setup path and how the answer is presented.

Which ad platforms can I reach?

Meta Ads, Google Ads and Amazon Ads for both reads and confirm-gated writes, plus Shopify read-only for orders, revenue and products. The MCP covers those four and nothing else.

Do I have to pick one client?

No. The connection belongs to your Muze account, not to a client. Connect ChatGPT for daily questions and Claude Code for a weekly sweep if that suits you, and both reach the same authorized accounts.

Can any of them spend money without asking?

No. Every write previews first and waits for an explicit confirmation, whatever the client. New campaigns are created paused. Muze never holds or moves your ad budget, and never charges a percentage of your spend.

What does it cost to try?

Nothing. The free plan includes 25 read-only tool calls a month across all four platforms, with no credit card. Write actions such as pausing an ad, changing a budget or creating a campaign require a paid plan.