01 · Records and state owned
Detailed performance reports; campaigns, ad sets and ads; product catalogs and product data feeds; audience insights; and signal-health or signal-quality diagnostics.
Meta
Meta Ads
Meta Ads is a social-advertising anchor with a first-party open-beta MCP connector and Ads CLI that expose campaign reporting and management, catalog operations, audience insights, and signal diagnostics; Meta also now supports direct AI connections through a developer's own app and administrator-defined MCP rules.
Advertising & media buyingSystem of engagementBYO-UI-ready platform
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Pull detailed campaign-performance reports, inspect audience insights, review catalog and feed state, and access signal-health and quality information through a Meta-authenticated connection.
03 · Actions and write paths
Create and edit campaigns, ad sets, and ads; create product catalogs; add product data; and act on feed issues through the documented connector surface. Meta's July update also identifies budget changes and catalog updates as actions that MCP server rules can govern.
04 · Authentication and permissions
The standard MCP connector uses a secure Meta-authenticated ad-account connection and requires no developer credentials, API setup, or coding. A separate July 2026 path lets developers connect an AI application using their own developer app; MCP server rules can be configured by someone with full control of the business portfolio.
05 · Monitoring, approval, and recovery
Use Meta's MCP server rules to constrain agent actions at the business-portfolio and ad-account boundary. Rules can govern operations ranging from budget changes to catalog updates and require a person with full portfolio control to configure them.
06 · Limits and caveats
Meta labels the connectors open beta and describes availability for businesses of all sizes across regions. Supported AI platforms and setup details are maintained in a separate help page, and the July developer-app and server-rule capabilities are newly introduced rather than a mature fixed contract.
Agent access
MCP support
Official MCP serverVendor-native Ads MCP connector with developer-app and CLI pathsOpen beta; governance and developer-app paths updated 2026-07-16
Support: Official MCP server
Read scope: Detailed campaign reports, real performance data, audience insights, catalog/feed status, and signal-health or quality diagnostics.
Write scope: Documented connector writes include creating and editing ads, ad sets, and campaigns; creating catalogs and adding product data; and rule-governed budget or catalog changes. Exact tool parameters still require setup-time inspection.
Authentication: Meta-authenticated ad-account connection for the standard MCP connector, with no developer credentials or API setup required; alternatively, connect through an owned Meta developer app for deeper custom integrations.
Approval boundary: Have a business-portfolio controller define MCP server rules before enabling writes, then require task-level confirmation for campaign launch, budget changes, catalog replacement, product-data updates, or edits that materially alter delivery.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Meta ships them.
Single-platform patterns
- Meta creative testing and campaign control room
- Campaign exception cockpit
- Creative and policy review queue
- Budget pacing workbench
Multi-platform compositions
- Meta Ads + CRM or revenue system: campaign exception cockpit
- Meta Ads + analytics or warehouse + creative-production platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
4 recorded sources
MCPRepresentative source
https://www.facebook.com/business/news/meta-ads-ai-connectors ↗Open-beta status, connection paths, reporting and mutation groups, Meta authentication, owned developer-app support, and MCP server-rule governance.
- Publisher updated
- Jul 16, 2026
- BYO-UI reviewed
- Jul 22, 2026
Live first-party article body retrieved and reviewed on 2026-07-22; credentialed feature availability not tested.
APISource inventory
https://developers.facebook.com/docs/marketing-apis/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.facebook.com/business/ads ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://developers.facebook.com/docs/graph-api/webhooks/ ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.