autowhisper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTOWHISPER_BASE_URL | No | Override for self-host/staging | https://autowhisper.xyz |
| AUTOWHISPER_API_TOKEN | Yes | Your API token from AutoWhisper |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| autowhisper_cmoA | Send a natural-language instruction to your AutoWhisper AI CMO and get its reply. The CMO can add a product, generate on-brand content (UGC video, posts, images), approve items, connect social platforms, publish across 30+ networks, and report analytics. Examples: "Add my product https://mystore.com/widget and start the CMO", "Generate a UGC video for my product", "Publish the approved content", "How did last week's posts do?". To add a product, pass a product URL (the CMO extracts the image from the page) — a text-only description will not create it, and placeholder/stock images are rejected. |
| autowhisper_confirmA | Approve or decline a destructive action the CMO asked you to confirm (surfaced by autowhisper_cmo). Pass the message_id it gave you and decision "yes" or "no". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Each tool has a distinct purpose: one sends instructions to the AI CMO and retrieves responses, the other confirms destructive actions. There is no overlap or ambiguity.
Both tools follow the same naming pattern: 'autowhisper_' prefix with a descriptive verb ('cmo', 'confirm'). The convention is consistent and predictable.
With only 2 tools, the set feels minimal for a marketing automation assistant. While the single 'cmo' tool is highly capable, the count is borderline and could benefit from more specialized tools.
The tool set lacks granular operations for managing products, content, or analytics independently. Users must rely on unstructured natural language instructions to the CMO, creating potential dead ends and reliance on the CMO's inference.