Autowhisper Mcp

io.github.xnjiangPublished by GitHub account xnjiangv0.9.0Updated Nov 2, 2026

Drive your AutoWhisper AI CMO to generate and publish marketing content from any MCP client.

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

Connects an assistant to an AutoWhisper account to plan, generate, review and publish marketing content such as UGC videos, images and social posts.

What you can do
  • Connect, check status and list products or workspaces
  • Read product facts, materials and presets
  • Create, revise, resume or render explicit content requests
  • Plan marketing or discuss ambiguous creative requests with the CMO
  • Review the content feed, posts and connected platforms
  • Edit text, take explicit actions, confirm, and check credits and performance
When to use it
Useful when you already run marketing on AutoWhisper and want your assistant to turn a product into creatives, review previews and costs, and publish to connected accounts without switching to the web dashboard.
Requirements
An AutoWhisper account. Remote use needs an MCP client with HTTP transport and OAuth authorization on the AutoWhisper page; the local stdio option needs Node.js 18+ and can use an existing AUTOWHISPER_API_TOKEN instead of the approval flow. AUTOWHISPER_BASE_URL and AUTOWHISPER_CREDENTIALS can override the API origin and credential file path.
Before you install
Generation and CMO consultation consume AutoWhisper credits, so read the quoted cost and billing before rendering. Approving a feed item can render, charge and publish to connected platforms. Writes need a stable request_id; on an uncertain response query the original request_id or message_id instead of retrying. Keep AUTOWHISPER_API_TOKEN out of chat and source control; the local server stores credentials in a shared file.

Installation

In SourceWeft

  1. Open Autowhisper Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.xnjiang%2Fautowhisper-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "autowhisper": {
      "type": "http",
      "url": "https://autowhisper.xyz/mcp"
    }
  }
}

README

AutoWhisper MCP

English · 简体中文

Turn your product into marketing content from the agent you already use. AutoWhisper gives your agent access to the same products, creative tasks, review queue, publishing connections and results as the web dashboard. Make UGC videos, images and social posts; review the result, then publish to the accounts you have connected.

Connect your agent to AutoWhisper · Explore the companion Skill

Start with one product

  1. Connect this MCP server and authorize your AutoWhisper account.
  2. Give your agent a product URL, or choose an existing product in a workspace.
  3. Ask for a creative, inspect its preview and cost, then decide whether to render or publish.

Try these prompts:

“Show my products and connected accounts. Don’t start any generation.”

“For this product, prepare one UGC video. Show the preview and quoted cost before continuing.”

“Show which posts failed and how the published content performed.”

Connect by URL

For clients that support remote HTTP MCP and its authentication, use:

text
https://autowhisper.xyz/mcp

In Claude Code:

bash
claude mcp add --transport http autowhisper https://autowhisper.xyz/mcp

Then open /mcp, select AutoWhisper and authenticate. Other compatible clients use their own connector setup. Authorize on the AutoWhisper page; you do not need to paste a token into a conversation. An AutoWhisper account is required.

Prefer a Claude Code plugin that installs the Skill and MCP together? Follow the companion Skill quick start.

Local stdio alternative

For clients that need a local process, Node.js 18+ is required:

json
{  "mcpServers": {    "autowhisper": {      "command": "npx",      "args": ["-y", "autowhisper-mcp"]    }  }}

Ask the agent to connect to AutoWhisper. autowhisper_connect returns an approval link and picks up authorization without a restart. Skill and local MCP share ~/.config/autowhisper/credentials.json.

Already have an API token? Set AUTOWHISPER_API_TOKEN in the server environment or secret store. Keep it out of chat and source control.

SettingDefaultPurpose
AUTOWHISPER_API_TOKENOptionalExisting token; otherwise use the approval flow.
AUTOWHISPER_CREDENTIALS~/.config/autowhisper/credentials.jsonOverride the shared credential-file path.
AUTOWHISPER_BASE_URLhttps://autowhisper.xyzSelf-hosted or staging API origin.

What the tools do

TaskTools
Connect and choose a workspaceautowhisper_connect, autowhisper_status, autowhisper_products_summary, autowhisper_products
Read product facts, materials and presetsautowhisper_context
Create, revise, resume or render an explicit content requestautowhisper_create_content, autowhisper_update_task, autowhisper_task
Plan marketing or discuss an ambiguous creative requestautowhisper_cmo
Review content and inspect deliveryautowhisper_feed, autowhisper_posts, autowhisper_platforms
Edit text or take an explicit actionautowhisper_edit_content, autowhisper_action, autowhisper_confirm
Check credits and resultsautowhisper_wallet, autowhisper_performance

Use the read tools for facts; they avoid a paid CMO chat turn. Explicit supported content requests use context → create/update → confirmation/review → task query. Marketing judgment can use CMO consultation. All four direct-content tools require workspace_id; writes also require a stable request_id. Check the server-returned capabilities and next actions: a tool in source or a package does not guarantee it is enabled for every account.

Preview, rendering and publishing are separate

  • accepted acknowledges a request; applied means it reached the native task. Only delivery_complete=true confirms the requested deliverable is ready. A script or first frame is not a finished video.
  • Generation and CMO consultation use AutoWhisper credits. Read the quote and actual billing; charges, refunds and included usage are distinct. Inspect your wallet for your account’s current balance and terms.
  • Approving a feed item can render, charge and publish to connected platforms. Follow the returned confirmation. With no compatible account connected, it schedules nothing; connecting later does not retroactively publish it.
  • On an uncertain response, query the original request_id or CMO message_id before retrying. Reuse identical request payloads and IDs; do not start another charged turn to recover the first.
  • Use the server-returned preview approval and current revisions when resuming or rendering. previous_previews is history; current partial artifacts are not a completed result.
  • AutoWhisper can prepare content and marketing advice. Publishing does not guarantee traffic, sales or ad-campaign execution. Competitor research occurred only if the actual task returns evidence of it.

For the detailed workflow and API reference, see the AutoWhisper Skill.

MCP or Skill?

MCP supplies callable tools; the Skill teaches an agent when and how to use the workflow. Use MCP alone for tool access, or both for the guided product → preview → review → publish workflow. They use the same AutoWhisper account and native tasks.

Start with your product on AutoWhisper

Development

bash
npm ciAUTOWHISPER_CONTRACT_FILE=test/fixtures/agent_content_contract.json npm test

This builds TypeScript and runs offline contract/behavior checks. Regenerate the fixture from the Rails contract test (UPDATE_AGENT_CONTENT_CONTRACT=1) and src/content-contract.ts together when changing the API. A passing fixture is separate from production rollout or a real generation/publishing test.

License

MIT. The open-source license covers this client; hosted AutoWhisper usage follows the service’s account terms and credits.

Source: README.md at commit 8477c10

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.9.0LatestSep 27, 2026
  2. v0.8.0Sep 21, 2026
  3. v0.7.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts