From an AI prompt to a governed change.
AdUp sits between your AI and your platforms. Reads pass through. Every write becomes a proposal that has to clear your rules before it touches a live account.
Four steps, every time a write is involved.
The same flow runs whether the AI is shifting a budget on Meta or pausing an ad set on Google.
Connect
One-click OAuth per clientLink each client's platforms with official MCP integrations. Meta Ads is the official server; Google Ads, TikTok, LinkedIn, GA4, Search Console, HubSpot and Intercom connect through vetted connectors.
Propose
The AI drafts the changeYour team works in their AI assistant — Claude, Gemini or ChatGPT. Reads run freely. The moment the AI calls a write tool — a budget change, a pause, a new ad — AdUp intercepts it and turns it into a proposal instead of an action.
Approve
Your rules or a human decideKPI thresholds auto-approve safe changes (budget shift under 10% while ROAS is above 3). Everything else waits for a person — approved in one tap from Slack, Teams, Google Chat or email.
Execute & audit
The write runs, the log records itApproved actions execute against the platform API or its official MCP server. Every proposal — who drafted it, who approved it, what changed — lands in an immutable audit log.
One connector in your AI assistant. Your role and clients come with it.
Each employee adds the AdUp connector to their AI assistant — Claude, ChatGPT or Gemini — with a personal API key. There’s no per-platform setup on their end — the gateway resolves who they are, which role they hold, and which clients they can touch.
Platform access is connected once per client over OAuth. A client running only Google Ads simply won’t expose Meta tools.
.mcp.json
{
"mcpServers": {
"adup": {
"url": "https://gateway.adup.io/mcp",
"headers": {
"Authorization": "Bearer adup_sk_••••••••"
}
}
}
}The moment the AI tries to write, it becomes a proposal.
Your team prompts the AI as usual — “raise the budget on our best retargeting set by 10%.” Reads happen instantly. But the write tool call is intercepted at the gateway.
Instead of changing the account, AdUp captures the exact change, the reasoning, and the relevant KPIs, and turns it into a proposal with full context attached.
Proposal · Meta Ads
Northwind Coffee Co.
Claude proposes a budget change on Retargeting — Prospects:
Daily budget
€120 → €132
ROAS is 3.4× over the last 7 days — above your 3.0× auto-approval threshold for changes under 10%.
Your rules decide. Or a human does — in one tap.
Set KPI thresholds that auto-approve safe changes — for example, budget changes under 10% while ROAS is above 3. Anything outside the rules waits for a person.
Approvers get the proposal where they already work — Slack, Microsoft Teams, Google Chat or email — with Approve and Deny right on the message. No dashboard required.
adup-approvals
AdUpApp10:42 AM
@Priya — Gemini wants to raise the budget on Retargeting — Prospects (Northwind Coffee).
Approved changes run. Everything lands in the log.
Once approved, the action executes against the platform API or its official MCP server. The proposal closes out with a result.
Every step is recorded — who proposed it, which rule or person approved it, what changed and when. The Control Center is where you decide, per tool, what’s even allowed to reach this stage.
Control Center
meta-ads-mcp · 5 tools introspected
get_campaignsget_insightsupdate_campaign_budgetpause_ad_setcreate_campaignThe AI never holds the keys to your accounts. AdUp does — and it only opens the door when your rules say so.
See the pipeline on your own accounts.
Connect a client, set one approval rule, and watch the first proposal come through.