Add the server
Remote servers live under mcp.servers in your OpenClaw config, with a url, transport set to streamable-http, and optional headers. On a gateway that runs on a server or VPS, an MCP Ads API key in an Authorization header is the reliable setup: there is no browser sign-in to complete on that machine.
- Create an API key
In MCP Ads, open Manage → Connect MCP → API keys at https://mcp-ads.com/manage, name the key “OpenClaw” and create it. Copy it now: it is shown once.
- Add the entry to your OpenClaw config
Put the entry under mcp.servers. You can also add it in the Control UI under Settings → MCP, choosing Streamable HTTP and adding the same header.
OpenClaw config (mcp.servers){ mcp: { servers: { "mcp-ads": { url: "https://mcp-ads.com/mcp-slim", transport: "streamable-http", headers: { Authorization: "Bearer mcp_live_...", }, }, }, }, } - Check the connection
The doctor command connects to the saved server and reports what it finds. A tool list means the key and URL are right.
bashopenclaw mcp doctor mcp-ads --probe - Verify it works
The first real tool call should return the platforms connected in your MCP Ads dashboard and the accounts on each. An empty list means the server is reachable but nothing is connected yet.
Try this firstUsing mcp-ads, list the platforms I have connected and the accounts on each.
Or sign in with OAuth
MCP Ads supports OAuth, and OpenClaw can run it: save the server with auth set to oauth, then run openclaw mcp login. This should work, but we have not yet tested OpenClaw’s sign-in against MCP Ads end to end, so on a server the API key above is the path we recommend.
openclaw mcp set mcp-ads '{"url":"https://mcp-ads.com/mcp-slim","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login mcp-ads
# browser on another machine:
openclaw mcp login mcp-ads --code <code-from-the-redirect>While auth is oauth, OpenClaw ignores a static Authorization header on that server. Use one method or the other, not both.
Troubleshooting
- openclaw mcp doctor mcp-ads --probe fails with 401: the key is wrong, revoked, or missing the “Bearer ” prefix. Create a new key under Manage → Connect MCP → API keys and replace the header value.
- The header is set but calls are still refused: check that auth is not set to oauth on the same server. With OAuth on, OpenClaw ignores the static Authorization header.
- The OAuth redirect never arrives: the gateway is on a server and the browser is on your laptop. Copy the code from the redirect and run openclaw mcp login mcp-ads --code <code>, or switch to the API key.
- Tools load but no ad accounts are listed: the connection works and nothing is connected in MCP Ads yet. Connect your ad accounts in the dashboard and ask again.