Quickstart

1. Create an account

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

2. Connect an ad platform

Open Accounts and choose a platform. Adako asks it for the accounts you can reach, then lists them. Turn on the accounts Adako may work on. Free covers 1 ad account a month, Pro 5 and Agency 20, and an account you used keeps its place until the billing period resets; everything else stays connected but untouched.

• Google Ads needs read and manage access to the Ads account. Manager accounts are listed but cannot be made active.
• Meta Ads takes an access token from your own Meta app, made for a system user that has the ad account and a promotable Page. The token guide walks through it.
• ChatGPT Ads takes an advertiser API key you paste in. One key is one account.
• LinkedIn Ads signs in through LinkedIn. It appears where the deployment carries its credentials; write to support if you do not see the card.

If a token later expires, the platform card says needs re-auth; Reconnect, or a new pasted token or key, fixes it. Nothing else breaks: the other platforms keep working.

3. Add the URL to your assistant

Adako is one MCP endpoint:

https://adako.ai/mcpCopy

• Claude — Use Adako directly inside Claude. Setup takes about a minute.
• Claude Code — Connect from the terminal with one command.
• ChatGPT — Use Adako directly inside ChatGPT. Setup takes about a minute.
• Cursor — Add it from Cursor’s own settings.
• Codex — Connect from the terminal with one command.
• Gemini — Paste the MCP URL into Custom apps.
• Antigravity — One block in the shared mcp_config.json.
• Windsurf — Add one server to Cascade’s MCP config.
• Perplexity — Add Adako as a custom connector.
• VS Code — One server entry in mcp.json for agent mode.
• Grok — Paste the MCP URL into a custom connector.
• Qwen Code — One command, or one block in settings.json.
• Kimi — Two commands in Kimi Code.
• OpenClaw — Two commands: add the server, then sign in.
• Hermes — One block in the Hermes config.yaml.
• DeepSeek — Runs in DeepSeek’s harness, not the chat app.

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

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 are free and 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.
• Run that wasted-spend check across all my active accounts.

Your assistant sees a short tool list plus two routers per platform: one for reads, which you can allow once, and a _write router for changes, which asks each time. It finds the rest with search_tools. That is the tool surface.

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.
• Workflows — the routine for a review, a launch and a recovery.
• Monitors — daily rules, alert emails and weekly briefs.
• Tools reference — every tool with its risk badge and cost.
• REST API and API keys — for terminals, servers and CI.