Run your ads from Slack.

What this actually is, stated honestly

Slack is not an MCP client. It is a place where MCP-capable assistants live. So the accurate version of “run ads from Slack” is this: the AI agent in your workspace connects to Muze, and you talk to that agent in a channel. If your agent supports remote MCP servers, this works. If it does not, no amount of Slack configuration will change that.

What the agent gets is 149 tools: Meta Ads at 37, Google Ads at 41, Amazon Ads at 48, Shopify at 15, and 8 cross-platform tools. The same set every other client sees. Nothing is held back for chat clients and nothing extra is handed to developer ones.

Why a channel is a genuinely good place for this

Because the approval is visible. Everywhere else, a confirm-gated write is a private moment between one person and an assistant. In a channel, the preview, the confirmation and whoever gave it are all in the scrollback. For an agency that has to explain a budget change to a client three weeks later, that thread is the record.

It also removes the worst meeting in performance marketing: the one where someone asks what yesterday's spend was and three people open three dashboards and return three different numbers. One agent, one connection, one answer, posted where everyone can see it.

How connecting works

You need a Muze account with at least one connected ad or commerce account, and an AI agent in Slack that supports remote MCP servers. The connection is configured on the agent, not in Slack.

1. Create a Muze account and authorize your accounts. Sign up for Muze and connect Meta Ads, Google Ads, Amazon Ads or Shopify over OAuth. Access is scoped to the accounts you choose and can be revoked at any time.
2. Check that your Slack agent supports MCP. The agent needs to support a remote HTTP or SSE MCP connection. This varies by product and by version, and it is the step that decides whether the rest is possible.
3. Point the agent at the Muze endpoint. In the agent's own configuration, add Muze as a remote MCP server at https://backend.muzecmo.com/mcp, authenticated with OAuth or with a Muze API key in the X-API-Key header, depending on what the agent supports.
4. Verify in a channel. Ask the agent in Slack to list your connected ad accounts. If get_my_accounts returns them, the connection is live and the rest of the tools are available in that channel.

Before you connect a shared channel, decide who should be able to trigger a write. Anyone who can talk to the agent can ask it to prepare one, and anyone who can talk to it can confirm one.

The connection guide carries current per-client configuration detail.

What you can ask once it is connected

Channel questions work best when the answer is short enough to read without scrolling. Ask for the number and the reason, not for a full report.

• What did we spend yesterday across Meta, Google and Amazon? get_blended_performance, which returns all three against Shopify revenue in one call.
• Anything pacing badly this week? list_campaigns_detailed and list_amazon_campaigns for the connected accounts.
• Pause the ad set we agreed to kill in standup and post the confirmation here. pause_ad_set, previewed in the channel before it executes.
• What is the client's blended MER month to date? get_blended_performance with get_shopify_revenue for the denominator.
• Which competitor ads went live this week? scrape_competitor_ads and get_competitor_ads, sourced from the Meta Ad Library.

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.

A shared channel means shared reach. Anyone who can message the agent can ask it to prepare a write, so put the agent in a channel with the people who are allowed to spend money.

Where Slack is the wrong client

This is the client with the most caveats, so here they are plainly. Slack has no MCP support of its own, which means everything depends on the agent you run there. Some do not support remote MCP servers at all. Others support them but not the authentication method you want.

Threads also hold context badly compared with a dedicated chat client. A long diagnostic conversation belongs in Claude or ChatGPT, and the conclusion belongs in Slack. And a channel is not an audit log with permissions: it is a record that whoever is in the channel can read and act on. If a write needs an approver, decide who that is before you connect the agent, not afterwards.

One connection, four platforms

Meta Ads, Google Ads, Amazon Ads and Shopify all come through the same connection, which is what makes the channel answer useful. “What did we spend yesterday” is a boring question until it covers every platform at once and sits next to actual store revenue.

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

Is there a Muze Slack app?

No, and we are not going to imply otherwise. Muze is an MCP server. You reach it from Slack through an AI agent in your workspace that supports remote MCP servers. The agent makes the connection and you talk to the agent.

Which Slack agents work?

Any assistant that can connect to a remote HTTP or SSE MCP server and authenticate with OAuth or an API key header. Support varies by product and version, so check the agent's documentation before assuming it will work.

Can teammates in the channel change my campaigns?

If they can message the agent, they can ask it to prepare a write, and they can confirm one. That is a property of the channel, not of Muze. Put the agent where the people allowed to spend money are, and nowhere else.

Does a write still preview in Slack?

Yes. The preview and the confirmation both happen in the conversation, which is the main advantage of running this in a channel: the whole approval is in the scrollback where anyone can find it later.

Which platforms can I ask about?

Meta Ads, Google Ads and Amazon Ads for both reads and confirm-gated writes, plus Shopify read-only for orders, revenue and products. That is the full scope of the MCP and it does not vary by client.

What does it cost?

The Muze free plan includes 25 read-only tool calls a month. Writes require a paid plan. You keep paying your ad platforms directly, and Muze never takes a percentage of your ad spend.

Muze in other AI clients