AdKit

Connect OpenClaw to AdKit

Connect OpenClaw to AdKit with the CLI or an API key and manage Meta, Google, TikTok, and Reddit ads, whether OpenClaw runs locally or on a server.

Connect OpenClaw to AdKit and manage Meta, Google, TikTok, and Reddit ads. The CLI setup works whether OpenClaw runs locally or on a persistent server: OpenClaw sends you a public sign-in URL that you can open in your own browser.

Give OpenClaw this prompt:

Help me set up AdKit.

1. Install the CLI: npm i -g @adkit/cli
2. Run `adkit setup`. Keep the command running in the background if needed, read its output, and send me the login URL immediately.
3. Wait for me to finish login in my browser, then wait for the setup command to complete.
4. Run `adkit status`.
5. Run `adkit checkin --agent openclaw`.
6. Tell me if AdKit is connected and ready. If not, tell me what failed.

If you cannot install or run the AdKit CLI in this environment, stop and tell me to use the MCP setup instead.

Open the URL OpenClaw sends you. After you approve access, the waiting CLI process stores the connection where OpenClaw runs.

Alternative: MCP with an API key

Use this when OpenClaw cannot run the CLI.

  1. Run openclaw --version. Update OpenClaw if it is older than 2026.5.12; older versions do not include the live MCP verification commands below.
  2. Create a key under Devices & Keys. It is shown once, so copy it immediately.
  3. Add AdKit to OpenClaw, replacing adk_your_key:
    openclaw mcp set adkit '{"url":"https://mcp.adkit.so","transport":"streamable-http","headers":{"Authorization":"Bearer adk_your_key"}}'
    
  4. Run openclaw mcp reload, followed by openclaw mcp doctor adkit --probe.
  5. Ask OpenClaw to run the AdKit check-in tool with agentId: "openclaw".

Keep the key in OpenClaw's MCP configuration, not in an agent conversation.

Troubleshooting

adkit: command not found. The CLI is not installed in that environment. Run npm i -g @adkit/cli, then try adkit status again. On a server, make sure it is installed in the same environment OpenClaw runs in.

The setup command keeps waiting. Complete the sign-in URL OpenClaw sent you. The remote command must remain running until browser authorization finishes.

MCP shows zero tools. Re-run the openclaw mcp set adkit ... command above and check the header is exactly Authorization: Bearer adk_your_key (capital B, one space). Then run openclaw mcp reload and openclaw mcp doctor adkit --probe.

Rotate or revoke a key. Go to Devices & Keys in AdKit to revoke a key and create a new one, then update the MCP configuration. API keys don't expire on their own.

What you can do

Once connected, OpenClaw can pull your live campaigns, draft budget and targeting changes, generate ad creatives, and research competitors. Nothing goes live on its own: every change is saved as a draft for you to review and publish.

Need a hand? Reach out and we'll help.

Related docs