Muze AI
PlatformMuze MCPLiteResultsPricingTalk to SalesStart free trial

Connection guide

Connect Muze to your AI.

Use OAuth in hosted AI clients or a Muze API key in desktop and developer clients. Both connect to the same secure MCP endpoint and the same 150+ tools.

ClaudeChatGPTCursorSlackCodex

You need a Muze account with at least one connected Meta, Google, Amazon, or Shopify account. Account connection and API-key management stay inside the Muze app.

The Muze MCP endpoint

Use this URL in every supported client. Hosted clients will open Muze OAuth automatically.

https://backend.muzecmo.com/mcp

Hosted clients: OAuth

Claude.ai and supported ChatGPT workspaces can authorize Muze without copying an API key. Add the remote MCP URL, sign in to Muze when prompted, and approve the connection.

Claude

Claude.ai

  1. Open Settings → Connectors.
  2. Select Add custom connector.
  3. Enter https://backend.muzecmo.com/mcp.
  4. Complete the Muze OAuth flow, then start a new conversation.
ChatGPT

ChatGPT

  1. In a workspace with custom MCP apps enabled, open Settings → Apps.
  2. Create or add a custom MCP app and enter https://backend.muzecmo.com/mcp.
  3. Complete OAuth and enable the Muze app for the conversation.

ChatGPT availability depends on your plan and workspace permissions. OpenAI maintains the current custom MCP app requirements.

Desktop and developer clients: API key

Create a key on the Muze API Access page. Keys begin with mz_live_ and are shown once. Store the key securely; rotate it if it is ever exposed.

Cursor

Cursor and JSON-based MCP clients

Open Cursor Settings → MCP → Add new MCP server, or add this entry to the client's MCP configuration:

{
  "mcpServers": {
    "muze": {
      "url": "https://backend.muzecmo.com/mcp",
      "headers": {
        "X-API-Key": "mz_live_YOUR_KEY_HERE"
      }
    }
  }
}
Claude Desktop

Claude Desktop and Claude Code

Add Muze as a remote HTTP MCP server using the endpoint above and send your key in the X-API-Key header. Reload the MCP server list after saving the configuration.

Slack

Slack and other MCP agents

Point the agent's remote HTTP/SSE MCP connection at the Muze endpoint and authenticate with OAuth or an X-API-Key header, depending on what the agent supports.

Your first five prompts

Start with a specific account question or a clearly bounded job. Muze resolves the available accounts and calls the relevant tools.

List my connected ad accounts and summarize performance for the last 7 days.
Show my blended MER for the last 30 days.
Which Amazon search terms are spending without converting?
Compare Meta and Google ROAS this month and show where the gap is coming from.
Build a paused Meta campaign for our new product and show me the setup before creating it.

How write actions work

  • Preview before every write. The first call describes exactly what will change and asks for confirmation.
  • Explicit confirmation. Nothing changes until the tool is called again with confirm=true.
  • New campaigns and ads are paused. Creation cannot begin spending; activation is a separate action.
  • Shopify is read-only. Write tools are limited to the supported advertising platforms.

Troubleshooting

ProblemWhat to do
401 / invalid API keyCheck the header and key value, or rotate the key on the API Access page.
Write tool unavailableThe free plan is read-only. Use a plan that includes confirm-gated writes.
Quota reachedWait for the next monthly cycle or change your plan.
Tool not foundDisconnect and reconnect Muze so the client refreshes its cached tool list.
Connected but no accountsOpen Muze and connect at least one supported platform, then retry get_my_accounts.

Need help?

Email hello@muzecmo.com, or browse the tool reference to confirm the operation your client should call.