ACA MCP ops
Use this whenever an agent needs to operate Automated Client Acquisition through MCP.
The rule for bots
One agent, one job, narrow scope. Prefer deterministic tool calls and scripts for structured ACA ops; use the model for unstructured judgment only. Keep a human on irreversible actions (activate campaign, bulk enroll, send at scale, spend) until the error rate earns autonomy. Support a morning drift check on org, ICP, sequences, and mailbox health.
Connect
- Prefer the installed ACA connector when available.
- Production MCP URL:
https://www.automatedclientacquisition.com/api/mcp
- Auth: Bearer API key from ACA Settings → MCP / API (never commit or paste keys into skills, repos, or chat logs).
- Lead enrichment: MoltSets or QuickEnrich API key required when enriching contacts.
Before mutating
- Call
get_help (or list tools) if unsure of the current schema.
list_accessible_organizations and switch_organization when the user has more than one org.- Prefer idempotent creates (
create_lead) and check existing lists/sequences before duplicating.
Safe defaults
- Create lists and sequences as draft; do not activate large campaigns without explicit user confirmation.
- Do not invent emails or phone numbers.
- Prefer tagging source/signal on leads when recording pipeline work.
- On bulk enroll or Apify import, confirm scope and cost first.
Common jobs
- Leads/lists:
create_lead, bulk_create_leads, create_lead_list, list_leads, search_lead_pool, build_lead_pool_list
- Sequences/campaigns:
create_email_sequence, create_campaign, enroll_leads, update_campaign_status
- Inbox:
list_conversations, send_conversation_reply
- Strategy context:
list_icps, list_products
Handoffs
When working inside a multi-agent crew, follow the ACA crew handoff skill and keep ACA as the system of record for lead state.
1---2name: aca-mcp-ops3description: Use this when connecting to or operating ACA via MCP for leads, lists, sequences, campaigns, and replies.4---5# ACA MCP ops67Use this whenever an agent needs to operate Automated Client Acquisition through MCP.89## The rule for bots10One agent, one job, narrow scope. Prefer deterministic tool calls and scripts for structured ACA ops; use the model for unstructured judgment only. Keep a human on irreversible actions (activate campaign, bulk enroll, send at scale, spend) until the error rate earns autonomy. Support a morning drift check on org, ICP, sequences, and mailbox health.1112## Connect13- Prefer the installed ACA connector when available.14- Production MCP URL: `https://www.automatedclientacquisition.com/api/mcp`15- Auth: Bearer API key from ACA **Settings → MCP / API** (never commit or paste keys into skills, repos, or chat logs).16- Lead enrichment: MoltSets or QuickEnrich API key required when enriching contacts.1718## Before mutating191. Call `get_help` (or list tools) if unsure of the current schema.202. `list_accessible_organizations` and `switch_organization` when the user has more than one org.213. Prefer idempotent creates (`create_lead`) and check existing lists/sequences before duplicating.2223## Safe defaults24- Create lists and sequences as **draft**; do not activate large campaigns without explicit user confirmation.25- Do not invent emails or phone numbers.26- Prefer tagging source/signal on leads when recording pipeline work.27- On bulk enroll or Apify import, confirm scope and cost first.2829## Common jobs30- Leads/lists: `create_lead`, `bulk_create_leads`, `create_lead_list`, `list_leads`, `search_lead_pool`, `build_lead_pool_list`31- Sequences/campaigns: `create_email_sequence`, `create_campaign`, `enroll_leads`, `update_campaign_status`32- Inbox: `list_conversations`, `send_conversation_reply`33- Strategy context: `list_icps`, `list_products`3435## Handoffs36When working inside a multi-agent crew, follow the ACA crew handoff skill and keep ACA as the system of record for lead state.
seguelaCedric