The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Adako — careful ad ops for AI agents listing page.
アダコ · adako.ai
Adako is an MCP server and REST API that connects Claude, ChatGPT, Cursor and other assistants to Google Ads, Meta Ads, ChatGPT Ads, TikTok Ads and LinkedIn Ads.
Ask "how did my campaigns do last month?" and get an answer from the live account, in the account's own currency. Ask "raise that budget to 40 a day" and get a proposal you approve before anything moves. Created campaigns are always paused.
This repository holds the public pieces: the Agent Skills, per-client configuration, one-file installers, a Claude Code plugin, and the MCP Registry entry. The server itself is hosted.
233 tools across five platforms, plus Adako's own.
| Platform | Tools | What they cover |
|---|---|---|
| Google Ads | 70 | Search and Performance Max, keywords and search terms, budgets and bid strategies, assets and extensions, conversion actions, labels, schedules, geo, hourly and device reports |
| Meta Ads | 44 | Campaigns, ad sets and ads, image, video, carousel and app-install launches, audiences and placements, pixels, lead forms, creative fatigue |
| LinkedIn Ads | 34 | Campaign groups and campaigns, image, video, carousel and text ads, B2B targeting, audience forecasts, conversion rules, engagement metrics |
| TikTok Ads | 30 | Campaigns, ad groups and in-feed video ads, Spark Ads, video metrics, identities, pixels, creative fatigue |
| ChatGPT Ads | 23 | Chat card campaigns end to end, account limits, pixels, review verdicts |
| Adako | 32 | Connections and usage, tool discovery, proposals, diagnostics, monitors, briefs and reports |
Your client does not see 233 entries. It sees 16 tools callable by name plus 13 routers. Each
platform has a read router (google_ads, meta_ads, chatgpt_ads, tiktok_ads, linkedin_ads)
and a write router beside it (google_ads_write, meta_ads_write, chatgpt_ads_write,
tiktok_ads_write, linkedin_ads_write). Monitors have monitoring and monitoring_write, and
diagnostics only reads. A read looks like
google_ads(action="execute", tool_name="google_list_campaigns", arguments={...}), a change like
google_ads_write(action="execute", tool_name="google_pause_campaign", arguments={...}).
Looking things up never changes an account, so an assistant that asks permission per tool can allow
reads once. Every change runs through a _write tool, which asks each time and creates a proposal.
search_tools finds the right tool from your own wording and returns its exact call line, and it is
free. See adako.ai/docs/routers.
LinkedIn Ads reads are open to everyone: connect the member who administers the ad account and every report, structure and forecast tool works. A change needs that ad account added to Adako's LinkedIn application first — send the nine-digit id to support@adako.ai. The TikTok Ads tools are on the surface, but TikTok accounts cannot be connected until TikTok approves Adako's developer app.
Adako is built so that an assistant can be useful without being dangerous.
| Rule | What it means |
|---|---|
| Reads run immediately | Performance, structure, search terms, audiences. Nothing to approve. |
| Every write becomes a proposal | You see the object, the before and after values, and the daily cost before anything is sent. |
| Approval is yours | Confirm in the chat, or leave proposals in an inbox and approve them at adako.ai/approvals. Proposals expire after 48 hours. |
| Created objects are paused | Every campaign, ad set and ad Adako creates starts paused. You enable it yourself. |
| Almost nothing deletes | Eight tools remove something and each needs an explicit confirmation flag. Pause never routes to a delete. |
| Executed once | Each approved proposal carries an idempotency key. Approving twice reports the first result and repeats nothing. |
| Read-back on every write | The change is confirmed by reading the object back from the platform, not by trusting the response. |
| Tokens stay server-side | Your platform tokens are held encrypted by Adako and are never forwarded to the AI client. |
Details: adako.ai/docs/safety.
Two ways to authenticate:
Authorization: Bearer ak_live_your_key, where ak_live_your_key is replaced by the whole key
you copied, prefix included and nothing around it. Use it for clients that read a static config file.Pick your client.
Pro and Max: Settings → Connectors → Add custom connector. Paste the URL, click Add, then Connect and sign in.
Team and Enterprise: an owner adds it first under Organization settings → Connectors → Add, hovers Custom, chooses Web, and pastes the URL. Members then connect it from their own Settings → Connectors.
The number of custom connectors you can add depends on your Claude plan.
Same Connectors settings as Claude.ai — add the custom connector with the URL above, then sign in
when prompted. Desktop shares your Claude account, so a connector added on the web is available here
too. Full guide: clients/claude-desktop.md.
Then run /mcp inside a session and pick adako to sign in through the browser.
Add it once for every project with --scope user:
API-key variant, no browser step:
There is also a plugin that installs the server, the skills, a setup command and an operator agent in one step:
See clients/claude-code.md and plugin/.
Adako as the connection name and https://adako.ai/mcp as the MCP server URL.
Add a short description, choose the public endpoint connection option, and click Create.Full guide: clients/chatgpt.md.
One command, idempotent, and it leaves your other servers alone:
Or write the file yourself:
Full file: clients/cursor/mcp.json. Guide:
clients/cursor.md.
This repository is also a Cursor plugin, for the Cursor Marketplace:
.cursor-plugin/plugin.json adds the server and the skills in
skills/.
Or run the installer, which rewrites one table in the Codex config (C:\Users\<you>\.codex\config.toml on Windows or /Users/<you>/.codex/config.toml on macOS) and leaves the rest of the
file untouched:
Full file: clients/codex/config.toml. Guide:
clients/codex.md.
Or add the block by hand to C:\Users\<you>\.codeium\windsurf\mcp_config.json on Windows or /Users/<you>/.codeium/windsurf/mcp_config.json on macOS:
Full file: clients/windsurf/mcp_config.json. Guide:
clients/windsurf.md.
On a computer, open gemini.google.com/apps, or Settings → Connected apps, then scroll to Custom apps at the bottom, choose Add a custom app, and paste the URL:
Click Next and sign in. Leave the credential fields under Advanced features empty: Adako
registers itself. In a chat, type @ and pick Adako.
Guide: clients/gemini.md. Custom apps are still rolling out, with conditions
Google lists: a personal Google Account, English, the United States, 18 or over.
All three read one file, so Adako is added once. In the desktop app: Settings → Customizations,
then Open MCP Config. In the IDE: the agent side panel, … → MCP Servers. In the CLI:
/mcp, or the file itself — C:\Users\<you>\.gemini\config\mcp_config.json on Windows or /Users/<you>/.gemini/config/mcp_config.json on macOS (Linux: /home/<you>/.gemini/config/mcp_config.json). Use .agents/mcp_config.json for one project. After saving, press refresh beside
Installed MCP Servers and click Adako to sign in.
Antigravity signs in through the browser on the first call. Guide:
clients/antigravity.md.
Gemini CLI stopped serving free and Pro accounts on 18 June 2026 and now runs only on paid Gemini
and Gemini Enterprise API keys. If you are still on it, the older spelling works: httpUrl in
.gemini/settings.json in your home folder, with the extension manifests
gemini-extension.json and
clients/gemini-cli/gemini-extension.json. Separately,
agy plugin import gemini carries an existing setup into Antigravity.
.vscode/mcp.json in a workspace, or your user mcp.json:
VS Code handles the OAuth flow. Full file with the API-key variant:
clients/vscode/mcp.json. Guide: clients/vscode.md.
Add Adako as a custom connector: on the web at
perplexity.ai/computer/connectors, or Settings →
Connectors in the desktop app, then the URL above with OAuth. Custom connectors come with Pro, Max
and Enterprise. Guide: clients/perplexity.md.
skills/ holds eleven Agent Skills. adako is the operating procedure: the safety contract, the
tool-call contract, the tool map and the workflows. The others are focused: one per platform, one per
job.
| Skill | For |
|---|---|
adako | The operating procedure. Start here. |
google-ads, meta-ads, tiktok-ads, linkedin-ads, chatgpt-ads | One platform each: tools by job, rules, launch order |
launch | Creating a campaign safely on any platform |
performance-review | Answering "how are we doing" with numbers that hold up |
optimize | What to change after the review, and in what order |
creative | Copy limits and asset specs per platform, and the fatigue playbook |
monitoring | Monitors, alerts, briefs and reports |
skills/ into the .claude/skills/ folder in your
home directory (C:\Users\<you>\.claude\skills\ on Windows or /Users/<you>/.claude/skills/ on macOS).SKILL.md (the same file as skills/adako/SKILL.md) as a skill in settings.The server also ships short instructions on connect, so the skills are optional. They make long sessions noticeably steadier.
The same tools run over HTTP with an API key.
GET /api/v1/tools lists every callable tool. GET /api/v1/openapi.json is the machine-readable
contract, which n8n, Zapier and Make can import. Full reference:
adako.ai/docs/api.
The adako command line wraps the same endpoints for scripts and coding agents:
Its source is in cli/: plain ESM, no dependencies, Node 22 or newer. The published
package is @adako/cli on npm.
Read-only, so nothing can move:
Then, when you want a change:
Every one of those ends with a proposal you approve or reject.
Free includes 1 ad account and 30 tasks a month. Pro ($49/month) covers 5 ad accounts and 600 tasks a month, Agency ($149/month) 20 accounts and 5,000 tasks, and Enterprise is priced per contract. An account used in a billing period keeps its place until the period resets. A task is one billed change to an ad account; reads and connection, usage, proposal, discovery, diagnostic and resolver tools are free. Monitors, scheduled briefs and generated reports need Pro or above. Details at adako.ai/pricing.
adako.ai/docs — quickstart, one page per client, one page per platform, the tool surface, workflows, monitors, the full tool reference and the REST API.
support@adako.ai · security reports: see SECURITY.md · changes: see CHANGELOG.md
The skills and the client configurations in this repository are MIT — see LICENSE. The hosted Adako service is proprietary.