Meta official Meta Ads AI Connectors(Korean: Meta Ads AI Connector) to operate Meta ads directly using natural language. It consists of the Ads MCP server and Ads CLI, and was released as an open beta on 2026-04-29.
One-line responsibility: This skill handles only the live operations of Meta ads (creation, modification, budget, on/off) . Report analysis, diagnostics, installation verification, and planning are handled by sibling skills (see "Sibling Skill Pair Separation" below).
1. Connection / Setup
1-1. OAuth 2.0 connector flow (primary · recommended)
This is the official default authentication path. App creation, app review, and manual token copying are not required. The client (Claude) performs Meta Business OAuth login in the browser and automatically issues an access token.
- Endpoint:
https://mcp.facebook.com/ads - Standard: RFC 9728 Protected Resource Metadata + RFC 6750 Bearer
- OAuth scope:
ads_management ads_read catalog_management business_management pages_show_list
A. Claude Cowork / Desktop (primary path for non-developers)
- Settings → Connectors → Add custom connector
- Enter name + URL
https://mcp.facebook.com/adsinput - The browser opens and Meta Business OAuth login proceeds
- Select ad account / page + select permission level
- Verify the connection with a natural language prompt (e.g., "Show me my ad account list")
B. Claude Code (.mcp.json)
Do not include a static Authorization header. The OAuth connector flow handles authentication.
{
"mcpServers": {
"meta-ads": {
"type": "http",
"url": "https://mcp.facebook.com/ads"
}
}
}
1-2. Static token (Fallback · deprecated)
For development environments where OAuth is not possible, this is a fallback-only path. Issue a developer/system user token from Graph API Explorer and inject it as META_ACCESS_TOKEN Bearer. Since a regular static Bearer may return 403 for OAuth-protected endpoints, always try OAuth first , and this path has lower priority.
- Do not hardcode tokens
- in code or SKILL.md. Environment variables are injected only with the
${META_ACCESS_TOKEN}syntax
2. Permission levels
During OAuth login, the user selects a level. Write and payment actions require user approval every time they are executed.
| Level | Scope | Recommended |
|---|---|---|
| read-only | View and performance analysis only | Starting level (recommended) |
| read+write | Create/modify campaigns, ad sets, and ads; adjust budgets | During operations |
| financial | Payment and billing-related actions | Only when needed |
Revoke permissions: Revoke connector access in Meta Business Suite.
3. Workflow
- Verify connection — Starts in read-only mode, retrieves the list of ad accounts and pages, and confirms the targets.
- Collect operational intent — Receives the goal (conversions/traffic/reach), target ad account, budget, period, and creative in natural language.
- Creation/modification proposal — Presents the change proposal in a table with the campaign → ad set → ad structure. New resources are created in the PAUSED state.
- User approval — Write, budget, and payment actions require user confirmation before execution (see safety guards below).
- Execution — Executes only approved actions via MCP and returns the result ID and status.
- Verification/chaining — If needed, hands off to the Korea market audit or analytics skill (§7).
Supported operations
- Campaign / ad set / ad creation, management, and modification (natural language)
- Budget setting and adjustment (daily budget/lifetime budget)
- Ad creative registration and replacement
- Conversion pixel connection
- Performance analysis: spend / impressions / CTR / ROAS + breakdown
4. Safety guards (HARD)
| Guard | Rule |
|---|---|
| Default PAUSED | New campaigns, ad sets, and ads created via natural language are always PAUSED. Automatic activation is prohibited. |
| Activation approval | Obtain explicit user confirmation before turning on ads or starting spend. |
| Write approval | All write, budget, and financial actions go through user confirmation before execution (MCP also requires per-action approval). |
| Token non-exposure | Never output or store tokens in code, SKILL.md, or logs. |
Automatic activation, budget increases, or payments without approval are never performed under any circumstances.
5. Trigger keywords
Centered on live operations verbs (analysis, diagnosis, verification, and planning are excluded).
- Creation: "make me a Meta ad", "create campaign", "add ad set", "register new ad"
- Modification: "modify ad targeting", "replace creative", "change ad set"
- Budget: "change budget", "increase/decrease daily budget"
- On/off: "turn on the ad", "turn off the ad", "pause", "activate/deactivate campaign"
- General operations: "Meta ad operations", "manage ads with AI connector", "connect conversion pixel"
6. Input / Output
Input
- Goal (conversions/traffic/reach/engagement), target ad account and page
- Budget (daily/lifetime), period, targeting conditions, creative (image/video/copy)
- Permission level (read-only / read+write / financial)
Output
- Change proposal table (campaign → ad set → ad, budget, status=PAUSED)
- Execution results: created resource ID and status, summary of applied changes
- For performance queries: spend/impressions/CTR/ROAS + breakdown table
7. Chaining
- If a Korean market audit is needed at the final step,
moai-ads-auditMCP(own 50-check) ormoai-marketer:marketing-meta-ads-analyzerchaining with the skill. - If you organize the operational results into a diagnostic text deliverable,
moai-coworker:ai-slop-reviewer→moai-writer:korean-humanizechaining for AI pattern review + Korean AI te removal. (Not applicable to numeric/dashboard deliverables)
Recommended chain example:
marketing-meta-ads-manager (생성·운영)
→ moai-marketer:marketing-meta-ads-analyzer / moai-ads-audit MCP (진단)
→ moai-coworker:ai-slop-reviewer (진단 텍스트 검수)
→ moai-writer:korean-humanize (한국어 AI 티 제거)
8. Separating sibling skill pairs
| Skill | Owner (responsible) | Verb nature | Without overlap |
|---|---|---|---|
| marketing-meta-ads-manager (this skill) | Meta ads live operations (official MCP) | create·edit·budget·on/off | Operational verbs only |
| marketing-meta-ads-analyzer | Meta ads report analysis·diagnosis (read/report) | analysis·interpretation·report | "analysis/diagnosis/report" requests go to analyzer |
| marketing-pixel-audit | Pixel·CAPI installation verification | check·verify | "pixel installation check" goes to marketing-pixel-audit |
| marketing-campaign-planner | Campaign planning(cognitive bias) | planning·design | "campaign planning/strategy" goes to planner |
Judgment criterion: "Does it actually create, change, or turn on/off?" (=manager) vs "Does it read, interpret, verify, or plan?" (=sibling skill).