Connect OpenClaw — MCP setup

Steps

Open a terminal on the machine that runs OpenClaw.

Copy and run the add command below.

Add Adako

openclaw mcp add adako --url https://adako.ai/mcp --transport streamable-http

Copy and run the login command, then complete the Adako authorization screen in your browser.
Sign in
```
openclaw mcp login adako
```
Run openclaw mcp status to confirm Adako is connected, then ask your agent to use it.

~/.openclaw/openclaw.json — the same server by hand

{
  mcp: {
    servers: {
      adako: {
        url: 'https://adako.ai/mcp',
        transport: 'streamable-http',
        auth: 'oauth',
      },
    },
  },
}

Untested: the configuration follows OpenClaw’s documented format, but Adako has not been verified in it yet. The config file is JSON5 and the key is mcp.servers, not mcpServers. OpenClaw ignores a static Authorization header while auth is "oauth", so choose one route: the browser sign-in, or auth left out and headers carrying an Adako key from /keys. openclaw mcp doctor adako --probe explains a failing connection.

Test it

Ask for something read-only first. This call is free and changes nothing.

first prompt

Using Adako, tell me which ad accounts are connected.

You should get back what is connected, which account is active, and two or three prompts worth trying next. If nothing is connected yet, the answer says so and links to the Accounts page.

When a write comes back as a proposal

Under the inbox policy, a write returns a proposal id and a diff instead of a result. Say “approve it” in the chat, or open Approvals and approve it there. Under direct, your confirmation in the chat is the approval.