Muze Ecommerce Ads

com.muzecmoPublished by muzecmo.comOfficial publisherv1.0.0Updated Oct 24, 2026

Run your ecommerce ads from Claude & ChatGPT: Meta, Google, Amazon, Shopify (150 tools)

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant run ecommerce advertising across Meta, Google, Amazon and Shopify through a hosted remote endpoint.

What you can do
A remote MCP server for managing ecommerce advertising. According to its registry description it covers Meta, Google, Amazon and Shopify and exposes roughly 150 tools, so an assistant can work with ad campaigns and storefront advertising data across those platforms from one connection. No tool list is published, so the exact operations are not documented here.
When to use it
Consider it when you run paid ecommerce ads on Meta, Google, Amazon or Shopify and want an assistant to handle campaign work across those channels instead of switching between platform dashboards.
Requirements
A remote streamable HTTP endpoint at backend.muzecmo.com; nothing to install locally. The manifest declares no authentication, environment variables or headers, but the provider's own account and platform connections are likely needed in practice.
Before you install
The manifest declares no authentication, yet the server is described as running live advertising accounts, so verify how access is actually authorized before connecting. Advertising tools can spend money and change or pause live campaigns; confirm which actions write or delete data and what account data is sent to the provider.

Installation

In SourceWeft

  1. Open Muze Ecommerce Ads in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.muzecmo%2Fecommerce-ads/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "muze-ecommerce-ads": {
      "type": "http",
      "url": "https://backend.muzecmo.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.