Liaison speaks MCP, the protocol AI clients use to reach external tools. In practice that means your ad account is available from Claude, or any other MCP client, without opening Liaison at all.
What it looks like
The same account, the same numbers, the same write layer underneath. A change requested from Claude arrives in Liaison as a pending card, born paused, waiting for your Confirm exactly as it would if you had typed it in the chat.
Why the guardrails live in the runner
An MCP client can ask for anything. That is the point of an open protocol, and it is also the reason the safety cannot live in the prompt: prompts are advisory, runners are not. Account scoping, the paused-by-default rule and the confirm step are enforced where the write happens, so a differently-worded request from a different client cannot talk its way around them.
Delete does not exist in the write layer, over MCP or anywhere else. When something has to be deleted, the answer is a link to Ads Manager.
Read from anywhere, write with intent
Reading is the natural fit: pull the week's numbers into whatever document you are already writing, ask for the ranked creatives while you plan next month, check lead quality without switching tabs. Writing works too, and it deliberately ends in the same place: a card in Liaison with your Confirm on it.
Getting connected
The gateway is available to accounts on the app today. Point your MCP client at the Liaison server, authenticate once, and your accounts appear as tools. If your team uses several ad accounts, the scope follows the account you select, as it does in the chat.