ACA - Automated Client Acquisition

com.automatedclientacquisition.wwwPublished by www.automatedclientacquisition.comOfficial publisherv1.0.2Updated Oct 24, 2026

Generate on-brand content, manage leads, and run outreach across 6 channels from your AI agent.

VerifiedSSEWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

ACA is a remote MCP endpoint that lets an AI assistant generate on-brand content, manage leads and run outreach across six channels.

What you can do
Generate on-brand marketing content from the assistant. Manage leads and contact records. Run outreach campaigns across six channels. Access is authenticated with an ACA API key sent in the Authorization header.
When to use it
Useful when you want an AI assistant to draft branded content, keep lead data current, or launch and manage multi-channel outreach without switching to the ACA dashboard.
Requirements
A remote SSE endpoint at the provider's site; no local package or runtime. An ACA account and an API key from the ACA dashboard (Settings > MCP / API), supplied as a bearer token in the Authorization header. Network access to the provider.
Before you install
Requires a live API key (cf_live_ prefix) in the Authorization header; treat it as a secret. Outreach tools may send messages to real contacts and change lead data, so review actions before they run. Content and lead data are sent to the ACA service.

Installation

In SourceWeft

  1. Open ACA - Automated Client Acquisition in the dashboard and add it to a workspace.
  2. Connect Authorization token 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 SSE. 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/com.automatedclientacquisition.www%2Faca/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.

{
  "mcpServers": {
    "aca-automated-client-acquisition": {
      "type": "sse",
      "url": "https://www.automatedclientacquisition.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.