Live now
Paid media
Meta Ads is the first working wedge for agent-operated marketing work.
Marketing operating system for agents
Operate your marketing stack through AI agents.
Connect Meta once today. Run performance reads, identify inefficiency, and move through marketing work with an agent. Analytics and other tooling are the next expansion layers.
Live now
Live todayMeta Ads
OperatorsClaude, Codex, Cursor
Setup pathApp + adcom
ExecutionHosted surface
Meta is the working wedge today. The broader operating system expands from that live path into analytics, reporting, and the rest of the stack.
Live today
Meta Ads
Operators
Claude, Codex, Cursor
Setup path
App + adcom
Execution
Hosted surface
Meta-first workflows
01
Review performance
Ask an agent for spend, clicks, CTR, CPC, and campaign-level movement without opening Ads Manager.
02
Find inefficiency
Use the same surface to flag weak campaigns or ad sets and turn raw performance into immediate next actions.
03
Operate with context
Keep setup, account context, and execution in one path so an agent can move from analysis into action cleanly.
First task after setup
Give the agent a real marketing read, not another setup step.
The first impression should be operational. Connect Meta in the app, then run the explicit-account review workflow instead of inventing your own first prompt.
Starter prompt
Use after connecting Meta in the app and starting the local adcom bridge.
You are connected to Ad Computer through the local adcom MCP bridge.
Call meta_get_ad_accounts.
Pick the first accessible Meta account_id.
Call meta_review_account_performance with that account_id.
Return the 7-day account summary plus the flagged campaigns and ad sets in priority order.Expansion categories
Next
Analytics
Bring site and performance context into the same operator workflow.
Next
Reporting and attribution
Turn channel data into decision-ready summaries and recurring operational reads.
Directional
Other marketing tooling
Expand from one live wedge toward a broader operating layer across the stack.
How it works
Connect once in the app. Operate through the agent after that.
The app handles identity and connection. adcom is there when a local or remote agent needs a stable path into the same operating surface.
01 Connect
Open the app, sign in, and connect Meta once in the browser.
02 Authorize
Use adcom when a local or agent-driven workflow needs credentials and context.
03 Operate
Run analysis and execution through your agent on top of one consistent surface.