Connect Qwen Code — MCP setup

Steps

Open a terminal in any project.
Copy and run the command below. Drop --scope user to add Adako to this project only.
Add Adako
```
qwen mcp add --transport http --scope user adako https://adako.ai/mcp
```
Start Qwen Code and run /mcp. The first connection opens the Adako authorization screen in your browser.
Ask Qwen Code to use Adako.

~/.qwen/settings.json — the same server by hand

{
  "mcpServers": {
    "adako": {
      "httpUrl": "https://adako.ai/mcp"
    }
  }
}

API key instead of the browser sign-in

{
  "mcpServers": {
    "adako": {
      "httpUrl": "https://adako.ai/mcp",
      "headers": {
        "Authorization": "Bearer ak_live_…"
      }
    }
  }
}

Untested: the configuration follows Qwen Code’s documented format, but Adako has not been verified in it yet. Use httpUrl, not url: url is the SSE field. Qwen Code finds Adako’s authorization server and registers itself, so no client id is needed. Use an API key from /keys where no browser is available. The Qwen Chat desktop app keeps its own MCP settings; these steps cover the CLI.

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.