logly/mureo

Commercial edition ·
日本語
**mureo** — your open-source, local-first AI ad ops crew. Find waste, audit changes, run ad accounts safely.
_Local-first. Strategy-grounded. Safety-gated._
Works with Claude Code, Cursor, Codex & Gemini. mureo sits on top of the official ad-platform MCPs and gives your AI a strategy to follow, an outcome to be measured against, and an audit trail you can show to anyone — **credentials never leave your machine**.
> Commercial editions are also available — including a cloud-hosted service and a local Agency edition for teams and agencies. See **mureo.jp**.
Real output: brand cannibalization auto-detected on a 30-day BYOD bundle (anonymized B2B SaaS account). More samples ↓
What is mureo?
mureo is a **local-first control plane for AI ad ops**. Once installed, AI agents (Claude Code, Cursor, Codex, Gemini, etc.) operate Google Ads, Meta Ads, Amazon Ads, TikTok Ads, Search Console, and GA4 *through mureo* — which keeps every action grounded in your business strategy, tied to real outcomes, and recorded in an audit log you can replay.
mureo ships its own connectors for Google Ads, Meta Ads, and Search Console today, and plugs in official ad-platform MCPs as platforms release them (TikTok's is already supported, and **Amazon Ads (official MCP bridge)** is bridged through mureo so your credentials never enter the host's MCP config — see docs/amazon-ads.md). mureo's value is not the API connection — it is **what happens around it**:
- **Strategy-grounded** — every decision reads STRATEGY.md (persona, USP, brand voice, goals)
- **Safety-gated** — rollback allow-list, GAQL guards, BYOD read-only by default, credential guard, per-platform throttle
- **Cross-platform** — Google Ads / Meta Ads / Amazon Ads / TikTok Ads / Search Console / GA4 in one workflow
- **Auditable** — append-only action log with rollback, plus a journal of *every* tool call and its outcome (mureo journal)
- **Local-first** — credentials never leave your machine
- **Learnable** — /learn builds account-specific knowledge over time
Quick start — see it work in 2 minutes
All you need is Python 3.10+ and Claude Code (Cursor, Codex CLI, and Gemini CLI work too — see Other agents and hosts). The **demo scenario** runs on synthetic data, so it needs no ad-account credentials, no OAuth, and no sign-up:
mureo configure opens a local browser UI (bound to 127.0.0.1, no remote access). Pick your Claude app, run the one-click basic setup, and then choose a **demo scenario** in the Demo / BYOD section. The UI also offers a platform-connection (OAuth) step — **skip it for now**; the demo doesn't need it. (Terminal equivalent: mureo setup claude-code --skip-auth && mureo demo init --scenario seasonality-trap.)
Then open the generated demo directory (the UI shows its path) in Claude Code and ask:
You'll watch the agent read the demo STRATEGY.md, pull campaign data, and walk into a seasonality trap that numbers-only tools miss. Try /search-term-cleanup next.
When you're ready to point mureo at *your* data, pick one of the two paths below.
Path A: Bring your own data (BYOD) — 5–10 min, no OAuth
**Export your real account data as an XLSX, drop it into mureo, and get a strategy-grounded multi-platform diagnosis** — no OAuth flow, no API-access approval. Import the bundle from the mureo configure dashboard (the same Demo / BYOD section), or from the terminal:
The first /onboard run interviews you and generates STRATEGY.md (your strategy) and STATE.json (state) — the context every later command reads. The demo skips this step because it ships with a ready-made STRATEGY.md.
Producing the XLSX is a one-time setup per platform — Google Ads via an Apps Script template (~5 min), Meta Ads via a 2-click Saved Report export (recognized in 9 languages). **BYOD guide →**
BYOD is **read-only by construction**: every mutation tool returns {"status": "skipped_in_byod_readonly"} — the agent analyzes and recommends but never writes to your account.
Path B: Go live (OAuth) — full functionality
Connect mureo directly to the Google Ads / Meta Ads APIs. Required to actually execute changes (running /rescue, /budget-rebalance, /creative-refresh, or applying a rollback via the rollback_apply tool) and for GA4 / Search Console support.
In the same mureo configure UI, open **Connect platforms**: interactive Google / Meta OAuth in the browser, with each field deep-linking to the right console page, plus official-MCP provider registration. (Terminal equivalent: mureo auth setup.) **Authentication guide →**