
ACA Automated Client Acquisition
ACA is an MCP server that generates on-brand content, manages leads, and runs outreach across 6 channels from your AI agent.
About
ACA (Automated Client Acquisition) is a remote Model Context Protocol server that bundles on-brand content generation, lead management, and outreach across six channels so a developer can run launch distribution from the same agent that built the product. Instead of exporting CSVs between a CRM, copy tools, and email sequences, you connect the SSE remote documented at automatedclientacquisition.com/api/mcp with a Bearer API key from Settings > MCP / API (format cf_live_...). Version 1.0.2 is positioned for growth-minded founders who already validated an offer and now need repeatable visibility—LinkedIn-style narratives, email touches, and coordinated touches depending on ACA’s channel map. Skillselion files it under Launch → Distribution because its headline promise is outbound and content motion, though you may reuse pieces during Grow for lifecycle nurture. Treat API keys as secrets in MCP headers. This is a commercial growth MCP, not Auth0 configuration or podcast research; results depend on your positioning and compliance with each channel’s rules.
- ACA Automated Client Acquisition MCP v1.0.2 over SSE at www.automatedclientacquisition.com/api/mcp
- Generate on-brand content, manage leads, and run outreach across 6 channels
- Authorization header required: Bearer cf_live_... API key from ACA dashboard (Settings > MCP / API)
- Website and product home: automatedclientacquisition.com
- Agent-native client acquisition stack rather than a single-channel social scheduler skill
ACA Automated Client Acquisition by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport sse aca https://www.automatedclientacquisition.com/api/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | SSE |
|---|---|
| Auth | Required |
What it does
Produce on-brand content, track leads, and execute multi-channel outreach from one agent-connected ACA remote MCP.
Who is it for?
Best when you have a live offer and want agent-driven client acquisition content and multi-channel outreach via ACA’s hosted API.
Skip if: Skip if you're still researching ideas with no leads list, or teams that cannot use a paid ACA API key and remote SaaS dependency.
What you get
One MCP-connected workflow produces branded assets, lead updates, and channel outreach plans you can execute without leaving the agent.
- On-brand content drafts aligned to ACA profiles
- Updated lead records and pipeline-oriented agent summaries
- Outreach execution plans spanning ACA’s 6 advertised channels
By the numbers
- Outreach coverage: 6 channels per product description
- Remote MCP transport: SSE at /api/mcp on automatedclientacquisition.com
- Published server version: 1.0.2
Recommended MCP Servers
How it compares
Hosted growth and outreach MCP with SSE auth, not developer identity admin or podcast transcript intelligence.
FAQ
Who is ACA for?
Developers and small teams using AI agents to run on-brand content, lead management, and outreach through Automated Client Acquisition.
When should I use ACA?
Use it at launch and early grow when you need distribution and multi-channel outreach tied to a managed lead pipeline.
How do I add ACA to my agent?
Configure the SSE remote https://www.automatedclientacquisition.com/api/mcp with Authorization Bearer cf_live_... from ACA Settings > MCP / API.