How to connect your ad accounts to OpenClaw

Add your advertising accounts to OpenClaw with one entry in openclaw.json. What to bound first, because OpenClaw runs unattended.

Both readings are on this page.

For you

What the answer looks like, and what to type to get it.

OpenClaw speaks the Model Context Protocol, so there is nothing to install. You paste one URL, sign in once, and your advertising accounts become tools it can call.

SetupLink to this section

json~/.openclaw/openclaw.json

{
  "mcpServers": {
    "get-mcp-ads": {
      "url": "https://mcp.getmcpads.com/mcp"
    }
  }
}

Restart the OpenClaw gateway. It supports both stdio and HTTP transports; this gateway is HTTP, so there is nothing to install locally.

Before it can answer anythingLink to this section

Connecting the client is one half. The other is connecting at least one advertising platform in the dashboard and ticking which accounts to expose. Both need you, not the assistant: one is a consent screen at Google or Meta, the other is a decision about which accounts a machine may read.

For your agent

The tool sequence, the parameters that matter, and what will be refused.

Both readings as Markdown: /guides/setup/openclaw.md

Setting up OpenClaw against this gateway. The endpoint is https://mcp.getmcpads.com/mcp, and each source also has its own endpoint if a narrower tool list is wanted.

Running unattendedLink to this section

An agent that runs without a person watching is the case this gateway is most careful about. The protections are the same as everywhere else, they just matter more here.

Keep the account on a plan without writes if nothing should ever change. Write tools are then absent from the tool list, not merely discouraged.
Tick only the ad accounts the agent should reach. The allowlist is checked server side on every call.
Every write still previews first. An unattended agent that calls a write once and never confirms changes nothing.
Watch the monthly call allowance. A loop that retries on error will spend it, and a refused call costs nothing but a failing loop still costs the successful calls before it.

What the client does on its ownLink to this section

It requests https://mcp.getmcpads.com/mcp and receives a 401 with a WWW-Authenticate header.
It reads the protected resource metadata named in that header.
It registers itself through dynamic client registration. No key is issued or pasted.
It opens the authorisation page with PKCE and waits for the person to approve.
It calls tools/list and receives the tools for the connected sources, plus four routing tools.

Checking it workedLink to this section

Call list_accounts. It answers without touching any advertising API, so it separates a connection problem from an account problem. An empty list means the platform is connected but nothing was ticked.