Email for agents
Let Claude, ChatGPT, Codex, Cursor, and other agents set up Loops, migrate your email, and draft campaigns.
What your agent can use
Connect over MCP, run the CLI, or build on the API. Each page shows it working.
MCP→
Connect Claude, ChatGPT, or another MCP client to your Loops account.
CLI→
Manage contacts, send events, and test transactional email from the terminal.
API→
Contacts, events, transactional email, campaigns, and content over REST.
LMX→
An email format your agent writes and edits through the Content API.
Skills→
Teach your coding agent the Loops API, CLI, LMX, and email best practices.
Workflows API→
Build workflows with triggers, timers, branches, and emails from code.
Set up with an agent→
Install Loops in your app and wire your API key, a contact, and an event.
Migrate with an agent→
Inventory your current sends and map each one to Loops before you switch.
What it looks like in practice
Detected Next.js. I installed the JavaScript SDK, wired LOOPS_API_KEY from .env, set up a contact sync route with a transactional send example, and wrote you a testing checklist.
I scanned your codebase and found every send, template, and webhook. Each one maps to a Loops equivalent, so I swapped the API calls and rebuilt your templates in LMX through the Content API.
Your Stripe webhook handler now calls the Loops events API when a subscription is canceled. I set the event name, mapped plan, reason, and date, and created the contact properties it needs.
I wrote the email in LMX, created a draft campaign, then added the subject, sender, and full content through the Content API. Tell me what to change and I’ll revise the copy.
Sent a test through the CLI with your transactional ID and sample data variables. The send came back confirmed, so check your inbox for the rendered email.