Adakoアダコ
DocsPricing
Sign inGet started
Dashboard
VS Code

接続Connect your AI

Connect VS Code

VS Code keeps MCP servers in mcp.json. Add Adako as one HTTP server and sign in once.

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.json
    {
  "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.
API key instead of the browser sign-in
{
  "servers": {
    "adako": {
      "type": "http",
      "url": "https://adako.ai/mcp",
      "headers": {
        "Authorization": "Bearer ak_live_…"
      }
    }
  }
}
Untested: the configuration follows VS Code’s documented format, but Adako has not been verified in VS Code yet. Tell support@adako.ai if a step does not match what you see.

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 Connections 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.