maxx-mcp

Run the full Maxx operator — brand, products, creative, campaigns, ads, research, distribution — from Claude Code (or any MCP client) over stdio.

Maxx is Claude + a tool registry (~130 tools). This package is a thin proxy: on start it pulls the live tool manifest from your Maxx server and advertises every tool; each call is forwarded to the server, which runs the real tool with your account context (credits, active brand, storage). The brain stays server-side — this is just the bridge.

Why an MCP (not just the web app)

The official Meta Ads MCP only works inside an allowlisted client (Claude Code / Claude Desktop / ChatGPT) — not a web app, and never via client-name impersonation. So the operator console is Claude Code itself: load maxx (this) alongside meta-ads and one agent orchestrates the whole loop — generate product shots → build the static-ad set → export the launch kit → push paused to Meta → pull insights — all legitimately (real Claude client + your own auth). Customers on the Maxx web app get the read-only connect + the launch-kit handoff instead.

Setup

1. Create an API key in Maxx → Settings → API keys (sk_live_…).
2. Add it to Claude Code:

claude mcp add --transport stdio maxx \
  -e MAXX_API_KEY=sk_live_xxx \
  -e MAXX_BASE_URL=https://sintetica.ro \
  -- npx -y maxx-mcp

3. Run /mcp to confirm it connected, then ask, e.g. "list my products", "build a static ad set for ", "export the launch kit".

MAXX_BASE_URL defaults to production; point it at a preview/localhost for dev.

Notes

• Async tools (image/video/static-ad generation) return a jobId. Poll it with the agent_job_status tool until status: completed to get asset URLs.
• Meta is read-only / advisory / handoff from Maxx — launching + spend changes are done by you (in your own Meta-connected Claude Code, or by importing the launch kit). Maxx never writes to a Meta account itself.