Before You Start: Which Path Are You On

Everything after this page follows the same three moves — be findable, earn trust, run ads — no matter how you drive AutoWhisper. The only fork is who’s clicking: you, in the dashboard, or an AI agent you already talk to every day, clicking on your behalf. This page settles that, then you’re free to move on.

The one-line test

Do you already have an agent that runs shell commands or speaks MCP — Claude Code, Cursor, n8n, that kind of thing?

• Yes → you’re on the agent path. You won’t open the AutoWhisper dashboard much; you talk to your agent, and AutoWhisper is the marketing department it just gained.
• No → you’re on the UI path. Go straight to the dashboard and follow Quick Start: 5 Minutes to Launch from signup. Every “click here” in the rest of the Playbook already means the dashboard — skip the rest of this page.

Both paths drive the exact same CMO under the hood. Neither is the “full” version. Pick whichever matches how you already work.

On the agent path: three steps

Step 1 — get your API token

Sign up (free credits are already on the account), then open Settings → Connect your agent and copy your token. It only ever drives your own CMO, and you can regenerate it any time to revoke access.

Step 2 — connect your agent: MCP client or skill, whichever it speaks

MCP client (Claude Desktop, Cursor, Cline, n8n): paste this into your MCP config and restart.

{
  "mcpServers": {
    "autowhisper": {
      "command": "npx",
      "args": ["-y", "autowhisper-mcp"],
      "env": { "AUTOWHISPER_API_TOKEN": "YOUR_TOKEN" }
    }
  }
}

CLI agent (Claude Code, clawdbot, that kind of thing): install the skill, then save your token locally.

npx skills add xnjiang/autowhisper-skill
mkdir -p ~/.config/autowhisper
echo '{"api_token":"YOUR_TOKEN"}' > ~/.config/autowhisper/credentials.json

Both routes reach the same capabilities — install whichever protocol your agent understands. You don’t need both.

Step 3 — the other half: your ads MCP

AutoWhisper plans the campaign and makes the creative. Actually getting an ad live is a separate MCP’s job. Use Meta’s own official Ads MCP — this is the page where you paste an API token, so we deliberately don’t pin any third-party package here. Get the connector straight from Meta: Meta’s Ads MCP documentation. Connect both MCPs together and your agent can go all the way from “here’s my product” to “this ad is live.”

Confirm which workspace you’re in

Skip this section if your account only has one workspace. But if you run more than one product line — a domestic workspace and an overseas one, say, or four brands in four workspaces — the following isn’t optional: the common way this goes wrong is chatting in a Chinese-language workspace and getting back a batch of English content, or connecting a platform in one workspace and finding it isn’t there when you switch to post from another.

• The generated content’s language is set by the workspace, not by the language you chat in. Chat entirely in English inside a Chinese-language workspace, and you’ll still get Chinese content — the workspace is the switch that decides output language, not your keyboard. Want something else, say so explicitly (“write this one in Spanish”).
• Platforms are connected per workspace. A TikTok or Instagram connection you made in workspace A isn’t visible — or postable — from workspace B. Each workspace’s platform connections are independent.
• CMO chat history is per workspace too. Switch workspaces and the conversation is empty — it’s not the same thread with a different backdrop.
• How to tell which one you’re in: in the dashboard, the workspace switcher in the top-left highlights the current one. From an agent, call GET /api/cmo/status — the response’s workspaces array lists each one with id, name, and content_lang, and the current workspace has current: true.

Which workspace are you working in right now? Confirm it with me before you do anything else, and stick to that one for the rest of this conversation.

⛔ Pass workspace_id explicitly on every call. Omit it and the API won’t error — it silently falls back to the first workspace on your account. You could think you’re managing four workspaces while everything actually keeps landing in the same one.

Next: The Three Moves: Why the Order Isn’t Optional — now that you know which path you’re on, here’s the order those three moves happen in and why skipping one burns ad spend.