Loops MCP. Manage contacts and trigger journeys programmatically.

You've got an AI agent that needs to handle customer comms? This server connects your agent straight to Loops, letting it manage everything from contact data to complex email journeys without you ever touching a dashboard. You control the entire lifecycle using natural language commands.

Managing Contacts and Data Status

You can keep track of every user record. To find out if a person exists, you just use find_contact with an email address, which returns all their current details. If that contact doesn't exist yet, you call create_contact, giving it the required email and optionally adding first or last names to build the record.

When data changes—like a user changing groups or updating their name—you use update_contact by specifying the target ID and listing all the fields you want to change. If that contact is garbage and needs deleting, you can permanently remove them using delete_contact; remember, this action's irreversible.

Before sending anything out, your agent must check if an address is eligible for mail; calling get_contact_suppression tells you immediately if the email has been flagged or bounced. This prevents sending messages to addresses that won't get seen.

Running Campaigns and Sending Messages

When you need to send a one-off, immediate message—say, a password reset link or an order confirmation—you use send_transactional_email. You provide the specific template ID and any variable data needed for that single email. If you're not sending a quick blast, but instead starting a complex workflow (like a welcome series), you send an event using send_event.

This triggers the platform to begin the automated journey for the specified user or recipient.

Segmentation and Utility Tools

You can’t segment people if you don't know what lists exist. To see all available groups, you run list_mailing_lists, which retrieves a list of every configured mailing list in your account. You also need to check the system itself; running test_api_key confirms that the API key your agent is using is valid and operational.

If you want to review recent communication activity, you can fetch a history of sent messages by calling list_transactional_emails, letting you limit how many results it returns. You have full control over contact records—you'll find tools to manage individual users via their ID or email address, check suppression status before mailing, and trigger complex journeys using event names.