Skip to content

logly/mureo

v0.9.10 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

advertising agentic-ai ai-agents claude-code cli codex
+11 more
cursor facebook-ads gemini-cli google-ads marketing marketing-automation mcp meta-ads model-context-protocol python search-console

Affected surfaces

auth

Summary

AI summary

Updates PRs in this release, Meta, and credentials across a mixed release.

Changes in this release

Feature Low

Adds optional `login_customer_id` field to GoogleAdsAdapter.account_credential_fields

Adds optional `login_customer_id` field to GoogleAdsAdapter.account_credential_fields

Source: llm_adapter@2026-05-25

Confidence: high

Feature Low

Publicly exposes `mureo.google_ads.list_accessible_accounts` and `mureo.meta_ads.list_meta_ad_accounts` functions

Publicly exposes `mureo.google_ads.list_accessible_accounts` and `mureo.meta_ads.list_meta_ad_accounts` functions

Source: llm_adapter@2026-05-25

Confidence: high

Full changelog

Optional login_customer_id + public account-listing helpers

Additive minor release on top of v0.9.9. Two coupled changes to the Google Ads / Meta Ads adapter surface, both ABI-non-breaking.

GoogleAdsAdapter.account_credential_fields gains optional login_customer_id

Previously only customer_id was declared as a per-account field; the MCC login_customer_id was treated as operator-shared. That works for the common single-MCC setup but stranded the case where one OAuth identity reaches accounts under different manager accounts.

login_customer_id is now an additional, optional field on the same declaration:

  • Leave blank to inherit the operator-wide MCC default — no behaviour change for existing single-MCC setups.
  • Set per account when the target customer_id resolves through a different MCC than the operator-wide default.
  • The parent_id field returned by mureo.google_ads.list_accessible_accounts for child accounts reached via MCC traversal is exactly the value account-picker tooling should populate here.

Adding a new entry to the tuple is purely additive — plugins reading it iteratively keep working.

Public-API surface for accessible-account discovery

list_accessible_accounts(credentials) (Google Ads) and list_meta_ad_accounts(access_token) (Meta) were previously defined inside mureo.auth_setup. They are now public:

  • mureo.google_ads.list_accessible_accounts — re-exported from the new mureo.google_ads.accounts module. Enumerates directly accessible accounts plus child accounts reached via MCC traversal.
  • mureo.meta_ads.list_meta_ad_accounts — re-exported from the new mureo.meta_ads.accounts module. Calls GET /me/adaccounts on the Graph API.

Both functions keep their original signatures and list[dict[str, Any]] return shape. The legacy import paths (mureo.auth_setup.list_accessible_accounts, mureo.auth_setup.list_meta_ad_accounts) are preserved as documented backward-compat re-exports — existing callers do not need to change.

Docs

docs/plugin-authoring.md gains a "Multiple account-level fields" subsection using the new Google Ads two-field declaration as the canonical example.

PRs in this release

  • #145 — feat(google-ads): optional login_customer_id per-account field + public account-listing helpers
  • #146 — release commit

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track logly/mureo

Get notified when new releases ship.

Sign up free

About logly/mureo

Framework for AI agents (Claude Code, Cursor, Codex, Gemini) to operate Google Ads, Meta Ads, and Search Console. Grounded in a local STRATEGY.md — not metric-chasing. Defense-in-depth security, local-first. Apache 2.0.

All releases →

Beta — feedback welcome: [email protected]