Connect
Bring your own Claude.Ripple brings the guardrails.
One hosted MCP endpoint puts your Meta and Google Ads accounts in front of the assistant you already use. It reads what Ripple has synced and asks Ripple for changes — and Ripple applies a change only if every one of your spend ceilings passes, then reads it back and keeps the undo.
Workspace preview
ONE WORKSPACE. YOUR ACCOUNTS.
Make the connection.
Northstar Studio · Demo
Northstar Studio · Demo
Select accounts. Review permissions. Stay in control.
Two minutes
Three steps, then a conversation.
No server to host, no OAuth app to register, no developer token to apply for. Ripple already did that part.
Here’s how it works.
Connect your ad accounts
Sign in with Meta and Google. Pick the ad accounts Ripple may see. Set the spend ceilings you want every change checked against.
Create a token
Read-only, or read-and-change. Scope it to some accounts or some tools if you like. Copy it once — Ripple keeps only a hash.
Paste one URL into your assistant
Claude Code, Claude Desktop, Cursor, ChatGPT, n8n — anything that speaks MCP over HTTP. Then ask a question.
MCP server URL
https://ads.ripplestrategies.ca/api/mcpStreamable HTTP, bearer-authenticated. The same address serves Meta and Google.
Connect
Your assistant asks.Your guardrails answer.
Other MCP servers hand your assistant the keys and hope it is careful. Ripple's tools cannot reach Meta or Google at all — every write becomes a proposed change that only executes if your daily and monthly ceilings, per-change limits and kill switches all pass. When one refuses, the tool says which, so the answer is a sentence instead of a surprise on the invoice.
- Read-only tokens, or tokens scoped to some tools and some ad accounts
- Every call logged with the token that made it
- Every executed change read back from the platform and reversible
Which of my Meta campaigns spent the most for the fewest leads this week?
↳ list_campaigns · 7 days
“Spring promo — broad” spent $612 for 4 leads ($153 each). Your other two campaigns are at $38 and $41 a lead. Want me to cut its budget?
Drop it to $40 a day and put the difference on the $38 one.
⊘ set_campaign_daily_budget · $120 → $40
Refused by a guardrail: “percentage budget-decrease limit exceeded” — your maximum step down is 50%. I can take it to $60 today.
Do that.
↳ set_campaign_daily_budget · $120 → $60 · executed · rollback: chg_7f2k
Done and read back from Meta. The other campaign is at $80 — the increase cleared every ceiling. Say “undo” and I roll either one back.
Your assistant
What your assistant can do.
Ask about your ads, make changes, and keep track of what happened — all in plain English.
Here’s how it works.
Get answers
Check spending and results, compare Meta and Google, and see what needs attention.
Make changes
Adjust budgets, pause or resume campaigns and ads, and block unwanted Google searches.
Stay in control
Review suggested changes before they run, check the change history, and undo supported changes.
Every change must pass your permissions and spend limits. Creating new campaigns or ads from chat isn't available yet.
Safety model
Four things that are true of every token.
The token is your assistant acting as you — never more than you.
Here’s how it works.
Mode is a ceiling
A read token cannot reach a write tool whatever else it is allowed. A write token needs your authenticator to create.
Your role bounds it
The token carries the permissions of the person who made it, re-read on every call. Lose the role, the token narrows with you.
Scope it down
Limit a token to some ad accounts and some tools. A junior buyer, a reporting bot and an agency client each get their own.
Every change crosses the executor
Daily, weekly and monthly ceilings, per-change limits, protected campaigns, the emergency stop — re-checked at the moment of the write, not when the token was made.
Memory, prompts, skills
It remembers you. It comes with a playbook.
A new chat used to start from nothing. Now the endpoint keeps a private notebook per person per workspace, serves seven ready-made workflows, and ships as a Claude Code plugin.
Here’s how it works.
Memory that is yours
recall at the start, remember at the end. What you decided, what to watch, what to check first next time — private to you in that workspace, listed on the Connect page, deletable in one click. Never a lead’s contact details.
Seven preset prompts
Catch me up, weekly review, budget pacing, search-term clean-up, what changed, leads pulse, save this session. Slash commands in Claude Desktop, Claude Code and Cursor; copy-paste anywhere else.
A plugin and the skills beside it
github.com/Dallenlol/ripple-ads-skills installs the skill, the prompts and the connector in two commands. Pair it with claude-ads for audits and planning across twelve platforms.
Claude Code
claude plugin marketplace add Dallenlol/ripple-ads-skills
claude plugin install ripple-ads@ripple-adsTry asking
Prompts that work on day one.
Here’s how it works.
- “Which of my campaigns spent the most for the fewest leads this week?”
- “Compare Meta and Google cost per lead over the last 30 days.”
- “Which search terms on my Google campaign are wasting money? Exclude the three worst.”
- “Pause every ad set with a cost per result over $60 this week and tell me what you paused.”
- “Undo the budget change you made this morning.”
- “What did Ripple change in the last two weeks, and what did each change do?”
Questions
Does this work with Claude Pro, or do I need the API?
Can the assistant spend money without me?
What happens when a change is refused?
Does it remember what we talked about last time?
Does it check my website too?
How fresh is the data?
Is there a free plan?
Which platforms?
Connect an account.Choose who runs it.
Point your own assistant at Ripple and work in chat, or start the agents in dry run and promote them when a week of decisions has earned it. The guardrails are the same either way.
Meta and Google Ads OAuth · You choose the accounts · Disconnect at any time
Workspace preview
YOUR BUSINESS, AT A GLANCE