Connect Kimi — MCP setup

Steps

Open ~/.kimi-code/mcp.json, or .kimi-code/mcp.json inside one project.
Add the adako block below beside any servers you already have, and save the file.
~/.kimi-code/mcp.json
```
{
  "mcpServers": {
    "adako": {
      "url": "https://adako.ai/mcp"
    }
  }
}
```
Start Kimi Code and run /mcp-config login adako, then complete the Adako authorization screen in your browser.
Run /mcp to confirm Adako is connected, then ask Kimi to use it.

On the older Kimi CLI, which reads ~/.kimi/mcp.json

kimi mcp add --transport http adako https://adako.ai/mcp
kimi mcp auth adako

Untested: the configuration follows Kimi Code’s documented format, but Adako has not been verified in it yet. A bare url means Streamable HTTP; add "transport": "sse" only for a legacy SSE server. On a machine with no browser, add "headers": { "Authorization": "Bearer ak_live_…" } with a key from /keys instead of signing in. /mcp-config also adds and edits servers without touching the file.

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.