_mureo-shared

mureo Shared Patterns

This file covers authentication, security rules, output formatting, and MCP configuration shared across all mureo skills (Google Ads, Meta Ads, Strategy).

Overview

mureo is a local-first control plane for AI ad ops. It sits on top of the official ad-platform MCPs (Meta Ads MCP, Google Ads MCP, etc.) and provides the layer they cannot — strategy enforcement, outcome correlation, and an auditable decision log. It provides:

• CLI (mureo) for direct command-line usage
• MCP Server for integration with AI agent hosts (Claude Code, Cursor, Codex, Gemini, etc.)
• Python library for programmatic access

All three interfaces share the same authentication, security rules, and output format.

Installation

pip install mureo

Setup

Claude Code (Recommended)

mureo setup claude-code

This launches a wizard that:

1. Asks which platforms to configure (Google Ads / Meta Ads)
2. Collects API credentials
3. Opens a browser for OAuth authorization
4. Lists accessible accounts for selection
5. Saves credentials to ~/.mureo/credentials.json

Manual Configuration

Create ~/.mureo/credentials.json:

{
  "google_ads": {
    "developer_token": "YOUR_DEVELOPER_TOKEN",
    "client_id": "YOUR_OAUTH_CLIENT_ID",
    "client_secret": "YOUR_OAUTH_CLIENT_SECRET",
    "refresh_token": "YOUR_REFRESH_TOKEN",
    "login_customer_id": "1234567890"
  },
  "meta_ads": {
    "access_token": "YOUR_LONG_LIVED_TOKEN",
    "app_id": "YOUR_APP_ID",
    "app_secret": "YOUR_APP_SECRET",
    "account_id": "act_XXXXXXXXXXXX"
  }
}

Environment Variable Fallback

If ~/.mureo/credentials.json is not found, mureo reads from environment variables:

Platform	Variable	Required
Google Ads	GOOGLE_ADS_DEVELOPER_TOKEN	Yes
Google Ads	GOOGLE_ADS_CLIENT_ID	Yes
Google Ads	GOOGLE_ADS_CLIENT_SECRET	Yes
Google Ads	GOOGLE_ADS_REFRESH_TOKEN	Yes
Google Ads	GOOGLE_ADS_LOGIN_CUSTOMER_ID	No
Meta Ads	META_ADS_ACCESS_TOKEN	Yes
Meta Ads	META_ADS_APP_ID	No
Meta Ads	META_ADS_APP_SECRET	No