npm autowhisper-mcpstdioMITupdated 7d ago
A marketing department for any MCP client (Claude Desktop, Cursor, Windsurf, n8n, …) — turn your product into batches of ready-to-run ad creatives (UGC video, posts, images), get advice on which creative to fund, and keep every channel alive across 30+ platforms, all in natural language.
Was kannst du mit autowhisper mcp machen?
AutoWhisper MCP
A marketing department for any MCP client (Claude Desktop, Cursor, Windsurf, n8n, …) — turn your product into batches of ready-to-run ad creatives (UGC video, posts, images), get advice on which creative to fund, and keep every channel alive across 30+ platforms, all in natural language.
It's the same CMO as the AutoWhisper dashboard, exposed over MCP. Honest scope: posting ≠ traffic — reach comes from your paid campaigns; this makes sure the creatives convert and your storefront doesn't kill them.
Install
Add to your MCP client config (Claude Desktop / Cursor / etc.):
{
"mcpServers": {
"autowhisper": {
"command": "npx",
"args": ["-y", "autowhisper-mcp"],
"env": { "AUTOWHISPER_API_TOKEN": "your_token_here" }
}
}
}
Get your token at autowhisper.xyz/skill → Settings → Connect your agent → Generate token. New accounts get free credits.
Tools
autowhisper_cmo— send an instruction to your CMO and get its reply. e.g. "Make a batch of ad creatives for my product https://mystore.com/widget", "Which creative should I run first?", "Keep my channels posted this week".autowhisper_products_summary— fast product counts by account/workspace. Use for "how many products do I have?" instead of spending a CMO chat turn.autowhisper_products— fast product list, with optional workspace/archive filters.autowhisper_status— fast CMO/account snapshot: products, feed, platforms, wallet, and automation settings.autowhisper_feed— fast CMO feed list with status counts and available approve/reject/dismiss actions.autowhisper_posts— fast post queue list, optionally filtered by status.autowhisper_wallet— fast credit balance.autowhisper_platforms— fast connected-platform list and connection health.autowhisper_action— direct approve/reject/dismiss/publish/reschedule/retry actions. High-impact actions return a confirmation id. Approving publishes: it schedules the piece to every connected platform, and a video draft also starts rendering and charges for it. With nothing connected it goes nowhere, and connecting later does not go back for it — the result says which happened.autowhisper_edit_content— direct title/body/hook/CTA/tone/keyword edits without a generation run.autowhisper_confirm— approve or decline any high-impact action the CMO or direct-action tool asks about.
Adding a product: lead with a product URL ("add my product https://mystore.com/widget") — the CMO extracts the image from the page. A text-only description won't create it (placeholder/stock images are rejected).
Asking for an ad plan:
autowhisper_cmoalso plans campaigns — "Give me a concrete ad-targeting plan for my product, starting markets, targeting, and what to avoid." The plan arrives as a card (markets, age, interest seeds, objective, which creative to run). It's prose for a human, in the owner's UI language — translate it before feeding it to an ad API. It suggests a starting platform, it doesn't lock one. It leaves out the budget (ask the owner) and gives interest search terms rather than platform IDs (resolve them in your ad tool). Grounded advice runs a live web search and can take over two minutes — if the tool times out, don't resend; that starts a second, separately charged turn instead of resuming the first. AutoWhisper plans and supplies creative; your ads MCP executes — never report that AutoWhisper "ran the campaign." No ads MCP connected yet? Don't name or install a third-party npm package for this — point the user at Meta's own developer docs instead: Meta's Ads MCP documentation.
One-time setup
To publish, ask the CMO to connect a social account — OAuth platforms return a link you click once. After that, publishing is hands-off.
Config
| Env var | Default | |
|---|---|---|
AUTOWHISPER_API_TOKEN |
— | required — your API token |
AUTOWHISPER_BASE_URL |
https://autowhisper.xyz |
override for self-host/staging |
License
MIT
Installation
autowhisper mcp zu deinem Client hinzufügen. Wähl den, den du nutzt.
claude mcp add autowhisper-mcp -- npx -y autowhisper-mcpcodex mcp add autowhisper-mcp -- npx -y autowhisper-mcpamp mcp add autowhisper-mcp -- npx -y autowhisper-mcp{
"mcpServers": {
"autowhisper-mcp": {
"command": "npx",
"args": [
"-y",
"autowhisper-mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"autowhisper-mcp": {
"command": "npx",
"args": [
"-y",
"autowhisper-mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"autowhisper-mcp","command":"npx","args":["-y","autowhisper-mcp"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"autowhisper-mcp": {
"command": "npx",
"args": [
"-y",
"autowhisper-mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"autowhisper-mcp": {
"command": "npx",
"args": [
"-y",
"autowhisper-mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"autowhisper-mcp": {
"command": "npx",
"args": [
"-y",
"autowhisper-mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"autowhisper-mcp": {
"type": "local",
"command": "npx",
"args": [
"-y",
"autowhisper-mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"autowhisper-mcp": {
"command": {
"path": "npx",
"args": [
"-y",
"autowhisper-mcp"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y autowhisper-mcpRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Unvollständig
- Dokumentation25/25
- Pflege25/25
- Vertrauen13/20
- Funktionsumfang0/15
- Installation12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 0 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Versionsverlauf
| Versionen | Veröffentlicht |
|---|---|
| 0.6.0Aktuell | 24. Aug. 2026 |
| 0.5.0 | 9. Aug. 2026 |
| 0.4.0 | 28. Juli 2026 |
| 0.3.0 | 27. Juli 2026 |
| 0.2.0 | 25. Juli 2026 |
| 0.1.0 | 15. Juli 2026 |