Use Amdahl with Cluster
Run Amdahl next to Cluster in the same AI client. Cluster finds the leads and sends the campaign, Amdahl writes each message, and your agent reports each send back to Amdahl.
Cluster connects to Claude, Codex, Cursor and other AI clients as an MCP server. Amdahl connects the same way. With both connected in one client, your agent can use Cluster for lists, signals and sending, and Amdahl for the copy.
The Cluster tool names below come from Cluster's own MCP tool list. We have not yet run the whole loop in a live Cluster workspace, from building the list to reporting the sends, so check your first campaign by hand.
Set up
- Connect Cluster to your AI client as a remote MCP server at
https://api.ethos.hello-cluster.com/mcp. It signs in with OAuth and needs no API key. - Connect Amdahl to the same client: see Connect your agent (MCP). Sign in with your work email and choose the Amdahl workspace for the company the outbound is for.
- In Claude, also add the Amdahl skill, as Connect your agent describes, so your agent sends outbound writing to Amdahl without being asked by name.
Running outbound for several clients? Use one Amdahl workspace per client. Ask your Amdahl contact about the Partner API, which creates a workspace for each of your clients.
The loop
- Check the client. One Cluster connection can reach several Cluster orgs. An Amdahl connection reaches only the workspace you chose at sign-in. Before any copy is written or loaded, have your agent call
get_current_ethos_organd confirm that the active Cluster org is the same client as the connected Amdahl workspace.list_ethos_orgsandswitch_ethos_orgchange it. - Find the leads in Cluster with
find_peopleorcreate_audience. - Write each message with Amdahl. Use
optimize_messagefor one recipient. For a whole campaign, useoptimize_message_batch, then read the messages withget_message_batch. Pass what Cluster found about each recipient as facts, such as their role, the company news and the reason to write today. A draft is optional. Keep each message'srun_id:optimize_messagereturns it, and for a batch it is on each itemget_message_batchreturns. - Load the messages into Cluster. A Cluster sequence is a template, so each recipient's message goes in a custom field on the list. Create the list with
create_listand itscustom_fields, or add recipients to a list withadd_contacts_to_list. Then build the sequence withcreate_campaign_with_sequence, with the email step's template referring to that field. Without the field, every recipient gets one shared body. Keep eachrun_idin a second custom field that the template does not use, so the reporting run can find it. - Launch with
launch_campaign, once you have read the campaign and approved it. - Report the sends in a later run. Cluster sends on a schedule over several days. Once emails have gone out, your agent reads each lead's send time with
list_campaign_leadsorget_campaign_progress, and callsreport_message_sentfor each lead that was sent: therun_id,provider: "other", thechannel,sent_as, the recipient, Cluster's campaign id asprovider_campaign_id, andsent_atset to the time Cluster sent to that lead. Run it again until the campaign is done. A send reported twice with the samesent_atis stored once. Amdahl stores the recipient and the text as hashes only. See Report sent messages.
An ask that builds the campaign:
Check that the active Cluster org is the same client as my Amdahl workspace.
Use Cluster to build a list of heads of RevOps at Series B SaaS companies that
are hiring SDRs. For each lead, use Amdahl to write the first email from what
Cluster found about them. Put each email and its run_id in custom fields on a
new Cluster list, and build an email sequence whose template uses the email
field. Show me the campaign before you launch it.An ask for a few days after launch:
For the Cluster campaign I launched on Monday, find each lead that has been
sent the first email, and when. Report each one to Amdahl with
report_message_sent, using the lead's run_id and the time Cluster sent it.What Amdahl sees
- Amdahl sees only what your agent sends it: the facts and draft for each message, and the send reports. It does not read your Cluster workspace.
- Amdahl does not get Cluster's replies yet. A send reported with
provider: "other"is stored, and Amdahl does not yet match it to whether it got a reply.