Quickstart

1. Create an account

Sign up with email or Google at /sign-up. New accounts start on Free with 15 tasks a month; system tools do not count.

2. Connect an ad platform

Open Connections and choose Google Ads or Meta Ads. Adako asks the platform for the accounts you can reach, then lists them. Pick one and make it active — plans allow one active account per platform, and everything else stays connected but untouched.

Google needs read and manage access to the Ads account. Meta needs a Business account with an ad account and a promotable page. If a token later expires, the platform card says needs re-auth and Reconnect fixes it.

3. Add the URL to your assistant

Adako is one MCP endpoint:

https://adako.ai/mcpCopy

• Claude — Claude apps and claude.ai, as a custom connector.
• Claude Code — One command in the terminal.
• ChatGPT — Developer mode connector.
• Cursor — A four-line file in your project.

The first connection opens a browser tab, you sign in to Adako and approve the client. The client stores an Adako token — never your Google or Meta credentials.

4. Run the first prompt

Call start_here and tell me what is connected.

start_here is free. It answers with what is connected, which account is active and a few prompts worth trying next.

5. Ask a real question

Reads run immediately. Try one of these:

• Which campaigns spent the most last 30 days, and what did they return?
• Find search terms with spend and no conversions in the last 14 days.
• Show me ad sets still in the learning phase.

6. Approve the first change

Ask for a change — “pause the campaign with no conversions” — and Adako replies with a proposal: a summary, a field-level diff, the expected impact and any warnings. Approve it in the chat, or open Approvals and stamp it there. After it runs, Adako re-reads the object and reports what exists on the platform.

Where to go next

• Safety model — what Adako will never do.
• Tools reference — every tool with its risk badge and cost.
• API keys — for terminals, servers and CI.