Discover
Find the signal
Summarize performance, inspect Search terms, and isolate spend that is not converting.
list_search_terms
Google + Meta + LinkedIn Ads MCP
Paid ads, with a receipt.
Ask ChatGPT to inspect, plan, and change your account. You approve every write.
Action receipt
ACT-8F41
You
Increase Brand Search to $120 per day, but show me the change first.
Campaign
Brand Search | AU
Daily budget
$80.00
$120.00
Status
Paused
Paused
50% budget increase. No change has been made.
Waiting for approval
One conversation. The whole Search workflow.
Focused tools help the model do the right job in the right order.
Plan
Build the campaign on paper
Validate ad groups, keywords, RSA limits, locations, bids, and budget before creation.
plan_search_campaign
Control
Approve the exact change
Get a current-to-proposed diff, then use an expiring receipt to execute one write.
confirm_action
Messy queries in. Controlled decisions out.
Memorised turns raw account data into a proposal you can inspect. It does not hide the account, budget, or consequence.
- Account ID is visible on every write receipt.
- Dollar inputs are converted to micros inside the server.
- Arbitrary GAQL and generic mutations stay private.
See the work before the ad platform sees it.
The MCP separates proposals from execution and verifies the result after a confirmed write.
Current
- Daily budget
- $80.00
- Campaign status
- Paused
- Receipt
- None
Proposed
- Daily budget
- $120.00
- Campaign status
- Paused
- Receipt
- Expires in 10 min
Read current stateCreate receiptApprove onceVerify result
Ask for the signal, not the spreadsheet.
Connect once. Work from ChatGPT.
The local beta supports per-user Google, Meta, and LinkedIn OAuth, account selection, encrypted token storage, and one protected MCP endpoint.
- Connect the MCPUse the Streamable HTTP URL.
- Authorize an ad platformSelect the exact Google, Meta, or LinkedIn account.
- Ask a real questionStart with a read-only audit.
- Approve a receiptExecute one visible change.
Control is the product.
MCP annotations help the client behave safely. Server-side rules make the boundary real.
Scoped
Each user selects one Google customer and one Meta ad account boundary.
Reversible first
Status and budget changes ship before destructive operations.
No hidden retries
A write receipt is single-use and a failed mutation is not retried automatically.
Credentials stay server-side
Google refresh tokens and Meta access tokens are never accepted as MCP tool arguments.