Integrations
Two ad platforms.Any assistant that speaks MCP.
Ripple connects to Meta and Google Ads with approved, verified apps, and exposes both through one MCP endpoint. The list of planned platforms is a list, not a promise with a date.
Watching. Not touching.Ad platforms
What Ripple reads and changes today.
Meta Ads
liveFacebook and Instagram. Campaign, ad-set and ad status, budgets, bid targets, creatives, insights and breakdowns. App Review approved.
Google Ads
liveSearch and Performance Max. Campaign status, budgets, bid targets, search terms and negative keywords, insights and breakdowns. Google-verified app.
TikTok Ads
plannedNext in line when customers ask for it. Needs its own app review.
LinkedIn Ads
plannedAfter TikTok.
Microsoft Advertising
plannedSearch import first.
Pinterest, Snap, Reddit
plannedListed so nobody has to ask. No date.
AI clients
Use the assistant you already run.
One URL, one token. Per-client setup is on the guides page.
Claude
Add a custom connector and sign in — no token to paste.
Claude Code
One `claude mcp add` command with a header.
Claude Desktop
A four-line entry in claude_desktop_config.json through mcp-remote.
Cursor
Settings → MCP → Add server, URL plus header.
ChatGPT
Developer mode connectors take a Streamable HTTP URL with a bearer header.
Codex
MCP servers in config.toml.
n8n
The MCP Client node, with the token as a header credential.
Zapier
Zapier MCP consumes any remote MCP server.
Also
Where the data goes next.
CRM webhooks
Leads from Meta forms and Google, delivered to your CRM with a signed webhook and a retry queue.
Conversion feedback
Lead outcomes sent back to Meta and Google so the platforms optimise toward the leads that closed.
Scheduled reports
Weekly and monthly digests by email, and share links for clients that never need a login.
Questions