MCP server and CLI for ad accounts · Claude Code, Cursor, ChatGPT In private build
Let your agent work on your ad accounts. You approve what it changes.
One MCP address and a CLI for Meta, Google Ads and X Ads. Your agent reads, previews, edits and launches; whatever your permissions hold back waits in your inbox until a person approves it.
Sign up for launchIn private build. Sign up now and your account is ready at launch.
An agent sessionExample · sample account
YouPause the US ad sets above a $40 CPA this week, and launch the four new hook videos from our best ad.
→get_metrics · US Store (Meta) · ad sets · last 7 days
→submit_edits · pause “Broad 25-54” · cut
proposed · waiting in your inbox
→upload_media_from_urls → create_build → preview_launch
4 ads · 1 ad set · all paused · no errors
→submit_launch · fingerprint from the preview
proposed · waiting in your inbox
AgentThe pause and the launch are both waiting for your approval in Kata Ads. I will not resubmit them.
Key scope: propose · nothing changed in the ad account yet
01 · Connect
One address. One key per agent.
Add api.kataads.com/mcp to your MCP client. An owner or admin signs the agent in through the browser and picks the workspace and one of three choices. For scheduled agents, an owner or admin makes a key in the web app.
- Read only
- Read and propose: changes wait in your inbox
- Read, propose and apply: applied where each account's permissions allow
- A key can be limited to listed ad accounts; your agent only sees the tools its key can use
02 · Preview
A preview before every write.
Edits, launches, duplicates and copies are previewed first and the preview writes nothing. The submit must match the preview, and takes an idempotency key: the same request is never applied twice. Some changes also need a confirmation that the agent passes only after asking you.
- Spend: enabling, raising a budget or a bid, a live launch
- Live change: an object that is running (pauses are exempt)
- Large change: a budget move above 50%
03 · Approve
The agent proposes. A person approves.
With a propose key, or with a kind of action set to Approval, each change becomes an inbox row with before, after and why; a whole launch becomes one row. Nothing reaches the ad platform until a person approves it, and a value that moved in the meantime is skipped, not overwritten. Agents never approve.
04 · Limits
Hard limits, no delete, an undo for every edit.
Archive and delete are never offered to agents. Agents cannot cross the limits you set per ad account: off-limits campaigns, a minimum ad set age, a daily budget ceiling, a maximum budget change per day. Every applied edit is logged with which agent made it, and undo_edit restores the previous value under the same rules. Launches and copies are not undone: they are created paused, and you pause them.
05 · Tools and CLI
48 MCP tools, and the same in a terminal.
This list is generated from the build's tool registry. Neutral tools work the same on every connected platform; per-platform reads appear when that platform is linked. The kataads CLI calls the same tools, logs in by browser or API key, prints one JSON object per command with --json, exits 0 when done, 1 when refused or failed, 2 when waiting for a person, and ships a skill file for your agent. It is in private build and not published yet.
- read
get_workspacelist_ad_accountslist_objectsget_objectget_metricsget_permissionslist_inboxget_inbox_runlist_editsrequest_featurereport_issuelist_mediaget_launchget_buildfind_ads_by_postpreview_duplicatepreview_copylist_winnersestimate_remakeget_remake_jobget_night_shift_statuslist_night_shift_passesget_night_shift_passget_night_shift_reviewget_approval_policy- propose
preview_editssubmit_editsundo_editupload_media_from_urlscreate_buildupdate_buildpreview_launchsubmit_launchcancel_launchretry_failedfork_buildshelve_buildsubmit_duplicatesubmit_copyrequest_remake- Meta
meta_ads_list_accountsmeta_ads_listmeta_ads_getmeta_ads_insightsgoogle_ads_resourcesgoogle_ads_keyword_ideas- X
x_ads_resourcesx_ads_audience_estimate- CLI
loginaccountsbrowsemetricspermissionsinboxhistoryeditsmediabuildslaunchduplicatecopyfeedbackschemaskilldoctor
An agent holding your ad account login, or your agent through Kata Ads.
Questions
Can I use it today?
Not yet. The MCP server and the CLI exist in the build but are not live, and the CLI is not published. Sign up now and your account is ready at launch.
Which agents work with it?
Any client that speaks MCP over HTTP with OAuth sign-in or a bearer key, such as Claude Code, Cursor or ChatGPT, and any agent that can run a command line.
Can my agent launch new ads?
Yes, through the launch tools: it uploads media from links, builds the launch, shows you the preview and submits it. On Approval the whole launch waits in your inbox as one row.
Can it approve its own proposals?
No. Approving, and changing permissions, limits or keys, is for people in the web app only.
Is each call billed?
Pricing is not final. The planned pricing never meters running campaigns, agent calls included; only ad-making would cost extra.
Give your agent hands, and keep the last word.
Sign up for launchKata Ads is in private build. Sign up now and your account is ready at launch. See the whole product.