ACA Automated Client Acquisition vs Autowhisper MCP
A side-by-side look at the ACA Automated Client Acquisition and Autowhisper MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
ACA Automated Client AcquisitionMarketingGenerate on-brand content, manage leads, and run outreach across 6 channels from your AI agent.37FairAuth: not declaredVerdict: choose ACA Automated Client Acquisition for marketing work; choose Autowhisper MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose ACA Automated Client Acquisition when
- You need dedicated capabilities in the Marketing domain.
Choose Autowhisper MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You want tools like
autowhisper_connect, autowhisper_products_summary, autowhisper_products.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A ACA Automated Client Acquisition | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 37/100 · Fair | 61/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 13 |
| Full listing | View ACA Automated Client Acquisition | View Autowhisper MCP |
Tools & capabilities
ACA Automated Client Acquisition tools
No tool names declared yet. Check the project README from the listing page.
Autowhisper MCP tools 13
autowhisper_connectAuthorise this MCP server against the user's AutoWhisper account. Returns a link; the user clicks Approve once and this server is authorised immediately — no restart, nothing to copy and paste. Call this when a tool reports it is not connected, or when a call returns Unauthorized. Show the user the link and tell them you are waiting.autowhisper_products_summaryFast read-only product counts, account-wide AND per workspace. Unlike the other read tools this one spans EVERY workspace — use it for 'how many products do I have in total?' and to discover workspace ids.autowhisper_productsFast read-only product list for ONE workspace (the user's current one unless workspace_id is given). Use instead of autowhisper_cmo when the user only wants to list/search products.autowhisper_statusFast read-only CMO snapshot for the user's CURRENT workspace (products, feed, platforms, automation settings) plus the account-level wallet and a directory of EVERY workspace with its id. Call this first to learn which workspaces exist and which one is current — every other read tool defaults to the current one and does NOT span the others.autowhisper_feedFast read-only CMO feed list for ONE workspace (the user's current one unless workspace_id is given), with status counts and available actions. Use for pending review/feed/status questions.autowhisper_postsFast delivery-queue list for ONE workspace (the user's current one unless workspace_id is given). Use for scheduled, failed, and published post facts.autowhisper_walletFast read-only credit balance. Use before proposing or starting credit-spending generation.autowhisper_platformsFast read-only connected-platform list and connection health for ONE workspace (the user's current one unless workspace_id is given).autowhisper_performanceRead-only cross-channel results for ONE workspace: a four-layer funnel, a per-channel breakdown, and ad spend over the window. Use this to answer how published content is actually doing, and before advising which creative to fund or scale — autowhisper_feed and autowhisper_posts only say what was made and sent, never whether it worked. ad_spend_cents is null (not 0) when the account has no active workspace: null means we cannot answer, 0 would assert nothing was spent.autowhisper_actionRun an explicit feed or post action without an AI chat turn. High-impact actions return a confirmation message_id; confirm it with autowhisper_confirm. approve_feed_item PUBLISHES: it schedules the piece to every connected platform, and for a video draft it also starts the render and charges credits for it — approving is the spend, not a bookmark. When nothing is connected it schedules nothing, and connecting a platform later does NOT go back for it; the result line says which happened. regenerate_content rewrites an existing draft IN PLACE (same record id, new text) — it is the same action as the Revise button on the web feed card; it takes content_type + content_id, not feed_item_id, and always returns a confirmation because it spends credits.autowhisper_edit_contentDirectly update exact content fields without a generation run or credit spend. Pass body for the full replacement copy/story. IDs: content_id is the CONTENT id — in autowhisper_feed output that is the `content: <type> #<id>` part of a row, NOT the leading `feed_item #<id>` (that one belongs to autowhisper_action). content_type is the same snake_case value shown there.autowhisper_cmoSend a natural-language instruction to your AutoWhisper AI CMO and get its reply. Best at: (1) generating batches of on-brand ad creatives (UGC video, posts, images) for paid campaigns, (2) advising which creative to fund and how to target, (3) keeping every social channel alive across 30+ networks, plus analytics. Examples: "Make a batch of ad creatives for my product https://mystore.com/widget", "Which creative should I run first, and how should I target?", "Keep my channels posted this week". Honest scope: posting ≠ traffic — reach comes from the user's paid ads. 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.- +1 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ACA Automated Client Acquisition
No confirmed install command for ACA Automated Client Acquisition yet — follow the setup steps linked from its listing page rather than a guessed package name.
Autowhisper MCP
{
"mcpServers": {
"autowhisper-mcp": {
"command": "npx",
"args": [
"-y",
"autowhisper-mcp"
]
}
}
}
Frequently asked questions
ACA Automated Client Acquisition is categorized under Marketing and uses an install path we have not confirmed yet. Autowhisper MCP belongs to Marketing and uses a local stdio subprocess. Pick ACA Automated Client Acquisition for marketing work and Autowhisper MCP for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. ACA Automated Client Acquisition has no confirmed install command yet — follow its own setup instructions.
ACA Automated Client Acquisition has no declared pricing — check the project's own site. Autowhisper MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aca-automated-client-acquisition-2 and autowhisper-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ACA Automated Client Acquisition has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Autowhisper MCP has 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars.