MCP server connecting Google Ads + Reddit Ads + GA4 into one AI-driven feedback loop inside your IDE.

uv sync                  # Install dependencies
uv run adloop init       # Interactive setup wizard
uv run adloop            # Start MCP server
pytest                   # Run tests
python scripts/sync-rules.py  # Sync rules: .cursor/rules/ -> .claude/rules/

src/adloop/
├── __init__.py        # Entry point — routes 'adloop init' vs MCP server
├── server.py          # FastMCP server — all tool registrations + toolset tags
├── config.py          # Config loader (~/.adloop/config.yaml)
├── auth.py            # OAuth 2.0 (user-supplied credentials, headless fallback) + service accounts
├── cli.py             # Interactive setup wizard (own Google Cloud project + auto-discovery)
├── crossref.py        # Cross-reference tools (GA4 + Ads combined)
├── tracking.py        # Tracking validation + code generation
├── ga4/               # GA4 Data + Admin API (reports, realtime, events)
├── ads/               # Google Ads API (read, write, GAQL, forecasting, PMax, recommendations)
├── reddit/            # Reddit Ads API v3 (own OAuth app, REST client, reads, PAUSED-creating writes)
└── safety/            # Guards, previews, audit logging

All tool usage rules, safety protocols, orchestration patterns, GAQL reference, GDPR awareness, and marketing best practices live in a single canonical file:

Read and follow .claude/rules/adloop.md for all AdLoop MCP tool orchestration.

That file is the complete guide for combining AdLoop's tools. It covers:

• Tool inventory with parameters and when to use each
• 9 safety rules (budget caps, dry-run defaults, Broad Match prevention, pre-write validation)
• 16 orchestration patterns (performance review, PMax analysis, recommendations, ad creation, tracking diagnosis, etc.)
• GAQL quick reference with syntax, common queries, and gotchas
• GDPR consent awareness for EU markets
• Ad copy character limits and marketing best practices

User docs live in the sibling repo ../adloop-docs (Mintlify, docs.getadloop.com — push to main deploys). After any tool or toolset change here, regenerate the docs tool reference and push it:

cd ../adloop-docs && uv run --project ../adloop python scripts/generate_tools.py

reference/tools.mdx is generated from the live registry — never edit it by hand, and never state tool counts in prose anywhere (they rot).

• Two-step writes: draft -> preview -> confirm_and_apply
• dry_run=true by default; require_dry_run in config overrides
• two_phase_apply in config: real applies refused (DRY_RUN_REQUIRED) until the plan had one dry-run pass; always on for cloud tenants
• Budget caps enforced; new campaigns/ads created as PAUSED
• Broad Match + Manual CPC automatically blocked
• All mutations logged to ~/.adloop/audit.log