Skip to content
Integrations

Every platform your clients run on, governed the same way.

Connect ad platforms and analytics over OAuth, route approvals to the channels your team already uses, and put any MCP server under AdUp's control.

Platforms

Ad platforms, analytics, and CRM.

Meta Ads is the official MCP integration. Google Ads, TikTok, LinkedIn, GA4, Search Console, HubSpot and Intercom connect through vetted connectors.

Meta Ads

Official MCP

Google Ads

TikTok Ads

LinkedIn Ads

Google Analytics 4

Search Console

HubSpot

Intercom

Official MCP via OAuth

One-click OAuth per client. No tokens to copy.

AdUp injects each client’s OAuth token per request at the gateway, so your team never handles credentials and tokens never live in a prompt.

As platforms ship official MCP servers, AdUp routes to them directly. Until then, vetted bridge connectors fill the gap — the governance layer stays identical either way.

1

Pick the platform

Choose Meta, Google Ads, TikTok and the rest for a given client.

2

Authorize once

The client (or your team) grants access through the platform's own OAuth screen.

3

Tools appear, scoped

That client now exposes exactly its connected platforms — nothing else.

Notifications

Approvals where your team already is.

Proposal alerts with one-tap Approve and Deny land in the channel of your choice.

Slack

One-tap approve

Microsoft Teams

One-tap approve

Google Chat

One-tap approve

Email

One-tap approve

The Control Center

Govern any MCP server — vetted or custom.

Connect a server from the vetted catalog or paste a custom URL. AdUp introspects its tools and classifies each as read or write.

Set every write tool to allow, require approval or block. You decide what AI can touch — not the model, and not the server author.

Control Center

meta-ads-mcp · 5 tools introspected

Readget_campaigns
always allowed
Readget_insights
always allowed
Writeupdate_campaign_budget
Writepause_ad_set
Writecreate_campaign
Reads run freely. Each write is allow, approve, or block.

Reads pass through

Every read tool runs straight to the upstream server, scoped to what the user can see.

Writes are policy

Each write is allow, approve or block — and approvals run through your pipeline.

Everything is logged

Proposed, approved, executed — across every connected server, in one audit trail.

Governed by default

Connect a platform in minutes.

OAuth a client, set your write policies, and you're governed end to end.