Connect VS Code

Steps

1. Create .vscode/mcp.json in your workspace, or open your user-level mcp.json to make Adako available in every workspace.
2. Add the adako entry below beside any servers you already have, and save the file.
   .vscode/mcp.jsonCopy

   {
     "servers": {
       "adako": {
         "type": "http",
         "url": "https://adako.ai/mcp"
       }
     }
   }

3. Start the server when VS Code offers to, and complete the Adako authorization screen in your browser.
4. Open Chat in agent mode and ask it to use Adako.

{
  "servers": {
    "adako": {
      "type": "http",
      "url": "https://adako.ai/mcp",
      "headers": {
        "Authorization": "Bearer ak_live_paste_your_key_here"
      }
    }
  }
}

Replace ak_live_paste_your_key_here with the key you copied from /keys — the whole value, including the ak_live_ prefix, and nothing else around it. Create an API key.

Test it

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

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.