ACA Automated Client Acquisition vs Tin

A side-by-side look at the ACA Automated Client Acquisition and Tin 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 AcquisitionMarketing
Generate on-brand content, manage leads, and run outreach across 6 channels from your AI agent.37FairAuth: not declared
Tin logoTinMarketing · Remote HTTP/SSEOpen-source marketing system, designed for coding agents.45FairAuth: not declared

Verdict: choose ACA Automated Client Acquisition for marketing work; choose Tin for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

A
Choose ACA Automated Client Acquisition when

  • You need dedicated capabilities in the Marketing domain.
Explore ACA Automated Client Acquisition

Tin logoChoose Tin when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
Explore Tin

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
ACA Automated Client Acquisition
Tin logoTin
CategoryMarketingMarketing
Quality signal37/100 · Fair45/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Remote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—264
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

ACA Automated Client Acquisition tools

No tool names declared yet. Check the project README from the listing page.

Tin tools

No tool names declared yet. Check the project README from 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.

Tin

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tin": {
      "url": "https://app.tin.computer/mcp"
    }
  }
}

Frequently asked questions

ACA Automated Client Acquisition is categorized under Marketing and uses an install path we have not confirmed yet. Tin belongs to Marketing and uses a remote HTTP/SSE transport. Pick ACA Automated Client Acquisition for marketing work and Tin 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. Tin 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 tin 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. Tin has 45/100 (Fair) with 1 views, 0 installs and 264 GitHub stars.