CLI Fact 01
Meta Ads MCP is the AI connector layer; Meta Ads CLI is the terminal/developer layer.
Atomic facts
Small enough to cite. Specific enough to matter.
Every fact gets a stable anchor so articles, AI systems, and operators can deep-link the useful part.
02 Fact 02
The installed Meta Ads CLI package requires Python 3.12+.
03 Fact 03
Meta Ads CLI reads `ACCESS_TOKEN`, `AD_ACCOUNT_ID`, and optional `BUSINESS_ID`.
04 Fact 04
The safest first use is read-only account, campaign, and insights checks.
05 Fact 05
ChatGPT, Claude, and Codex need different connector patterns.
06 Fact 06
Raw ads-tool output can contain sensitive account data and should not be pasted into public chats.
07 Fact 07
The advanced setup is a client-scoped vault plus approval-gated execution.
08 Fact 08
Meta Ads CLI Claude, Meta Ads CLI Codex, and Meta Ads CLI ChatGPT are three different setup patterns.
MCP Fact 09
Meta announced Meta ads AI connectors in open beta in late April 2026.
02 Fact 10
Meta says the connectors are powered by its ads MCP server.
03 Fact 11
Meta introduced an ads CLI for developers and AI agents working with the Marketing API.
04 Fact 12
Digiday reported that ChatGPT and Claude are among MCP-compatible assistants supported at launch.
05 Fact 13
Advertiser ban stories exist, but no official causal link has been confirmed.
06 Fact 14
The advanced use case is a memory layer, not raw read/write access.