Get the weekly radar
One short email with the freshest products, every week.
Harry lets an agency build and launch Meta ad campaigns by asking ChatGPT or Claude.
Grounded in available product and source data
Building a Meta ad batch usually means logging into a separate ad-ops platform and clicking through its own interface — Harry offers an AI media buyer inside ChatGPT and Claude instead, so a campaign draft can be built by just asking, wherever an agency already works.
Connecting Harry to an AI assistant runs through MCP, an open standard for connecting AI assistants to external tools, with the site specifically calling out that there are no API tokens to paste and no plugins to maintain — a one-click sign-in is enough, and Harry then operates inside the user's own account with the user's own permissions rather than a separate access layer. From there, a request as plain as 'create a draft Meta batch for this client using this template' is enough to produce a reviewable draft.
That plain-English request pattern extends beyond just building campaigns — asking which clients haven't had an updated ad batch in the last 30 days, or pulling recent file uploads from Google Drive into a new batch, both work the same way, treating campaign operations as something to ask for rather than manually assemble.
Critically, drafts still get reviewed inside Harry before anything actually launches, and launching uses a user's own existing safeguards rather than bypassing them — the AI assistant builds the draft, it doesn't unilaterally push live spend. Harry is positioned specifically for agencies managing multiple clients and campaign workspaces, with Meta Ads and Google Drive integrated today and Google Ads named as coming soon. The page reviewed does not specify what happens if a draft fails validation, worth confirming directly before relying on it for a time-sensitive launch.
It's designed to be minimal — one click to sign in, rather than a setup process involving generating and pasting API credentials into a separate settings page.
No — even a request phrased as 'launch this' still produces a draft that surfaces inside Harry for review first, rather than the assistant executing a live spend action from the chat itself.
The page reviewed does not detail cross-assistant state syncing, since Harry operates against the same underlying account and data regardless of which connected assistant is used at a given moment.
That depends on which channel matters most today — Meta Ads and Google Drive already work now, while Google Ads is only named as a future addition rather than something to wait on before starting.
Yes — multiple named campaign workspaces per client are supported, which keeps different clients' campaign work organized separately rather than in one shared workspace.
