A signup event in Loops can update a contact and start a published workflow, so an agent action may trigger more than a message. The Loops MCP server is hosted at https://mcp.loops.so and connects compatible AI clients to Loops account operations.
The Loops MCP server connects an MCP-compatible client to the Loops email platform through a remote server and browser-based OAuth. An authorized agent can find or update contacts, manage mailing-list membership, send events, and send published transactional templates; Loops also describes campaign, workflow, and email-content operations. This guide covers client setup, a sample event workflow, and safeguards for write actions.
What the Loops MCP server is and can do
The Model Context Protocol (MCP) lets an AI client call tools exposed by an external service. Loops operates the remote MCP server for its email platform, so the client connects to Loops rather than to a mailbox or a local server you install. Loops says its Claude directory connector uses the same server endpoint, https://mcp.loops.so.
Loops’ MCP page groups its main actions into four areas:
- Contacts: Find, create, and update contacts and their properties.
- Mailing lists: Check membership and add or remove contacts from lists.
- Events: Send events that update contact activity or can start a published workflow.
- Transactional email: Send a published template with data variables.
The page also describes the integration as a way to manage campaigns, workflows, and email content. These are documented capabilities; they should not be mistaken for a guaranteed list of five tool names that appears identically in every client. The practical distinction is the action: a contact update changes account data, while sending an event records activity and may trigger automation configured in Loops.
For example, if the signup event is configured to start an onboarding workflow, sending that event can place a contact into the workflow. Sending a transactional email is a different operation: it uses a published template and its data variables. Before an agent sends either, know which event or template your account is configured to use.
How to connect Loops MCP to Claude, ChatGPT, or another client
You need access to a Loops account and an MCP client that supports remote Streamable HTTP connections and OAuth using Client ID Metadata Documents (CIMD), or is preregistered with Loops. Loops’ documented connection uses browser sign-in, so you do not need to paste a Loops API key into the client configuration.
Use the client’s Loops connector when available, or add the hosted server as a remote MCP connection:
- Claude: Add Loops from Claude’s connector directory, then complete the browser sign-in and authorization.
- ChatGPT: Install the Loops plugin from the plugin directory and follow its authorization flow.
- Cursor: Loops points Cursor users to its CLI setup route. Follow the current Loops instructions for that client rather than copying a configuration command from another client.
- Another MCP client: Use
https://mcp.loops.soas the remote server endpoint and complete OAuth in the browser. Loops’ setup guides also cover Claude Code, Codex CLI, and VS Code.
After authorization, ask the client to perform a low-risk lookup, such as finding a contact you control. Confirm that the client exposes Loops actions and that the returned account data is from the intended Loops account before allowing writes. If a client requires a manually entered client ID or secret, check whether it supports the OAuth method Loops documents.
Example: create a contact and send a signup event
Suppose your app creates a Loops contact when someone registers, then uses a signup event to begin onboarding. A careful agent run should identify the intended contact first, create it only if needed, and ask for approval before sending the event.
Example prompt:
Find
sam@example.comin Loops. If no contact exists, create one withplanset topro. Then send thesignupevent to that contact with the event propertyplan: pro. Show me the contact and event details before you make either change.
Illustrative event data:
{
"event": "signup",
"properties": {
"plan": "pro"
}
}
Treat this as an example of the information to confirm, not a required API payload format. Your event names and properties need to match what your Loops account and workflow expect. The signup event and plan property are examples shown in Loops’ MCP material.
After approving the actions, inspect the contact’s activity in Loops for the signup event. If a published workflow is configured to respond to that event, check the workflow’s activity to confirm the intended path ran. A contact appearing in Loops confirms the contact action; it does not by itself prove that the event triggered the expected automation.
OAuth authorization and safe use
The documented authorization path opens Loops in a browser and uses OAuth; you do not provide an API key to the MCP client. Once connected, the integration can perform write operations such as updating contacts, changing mailing-list membership, sending events, and sending transactional email. Treat the connection as capable of writes, not as a read-only account lookup.
Before approving an action, review the target contact, the property values, the mailing list, or the event name and properties. For transactional email, confirm the published template and the data variables the agent will supply. This matters because an event may start a workflow, and a transactional send reaches a recipient.
We take a similar test-first approach with our own MCP server: it is available on every Volanea plan and has 23 tools. For API-key testing, Volanea’s sk_test_ keys render and log messages but never deliver them. That behavior is specific to Volanea, not a mode to assume for Loops. Our secure email MCP setup guide covers approval checks for agent-connected email workflows.
Choosing between Loops MCP and other email MCP options
The direct Loops connection is the clearest fit when your agent needs to operate on data and email workflows in a Loops account. Volanea is another option for teams that want transactional email, campaigns, and automations through one API; our guide to transactional email for AI-built apps explains our approach. These are separate products and MCP connections, not interchangeable server endpoints.
| Connection | What it connects an agent to | Authentication detail stated by the provider |
|---|---|---|
| Loops MCP | Loops contacts, lists, events, transactional email, and other documented account operations | Browser-based OAuth; no Loops API key is needed for the documented flow |
| Volanea MCP | Volanea’s email platform | Volanea’s MCP server has 23 tools and is available on every plan |
| A connection labeled Zapier MCP | A separate MCP connection, not the Loops endpoint at https://mcp.loops.so | The Loops setup information does not establish the tools or authorization model of a Zapier connection |
Choose based on where the relevant contacts, templates, and workflows live. A remote MCP hosting service solves a different problem: Loops already provides a hosted endpoint, so you do not need to deploy a server simply to connect an MCP-compatible client to Loops.
Troubleshooting a Loops MCP connection
If Loops does not appear or its actions are unavailable, check the connection in a few steps:
- The server will not connect: Confirm the client supports remote Streamable HTTP and use the exact endpoint
https://mcp.loops.so. - Authorization does not finish: Restart the Loops connection and complete the browser sign-in and approval flow for the account you intend to use.
- The client asks for an API key: The documented Loops flow uses OAuth. Check that your client supports Loops’ authorization method rather than entering credentials into an unsupported setup screen.
- An action succeeds but the expected result is missing: Check the contact activity, event name, and the published workflow or template involved. A workflow only runs when its configured trigger and conditions match.
For a first test, use a contact you control and an event whose workflow effects you understand. That lets you separate a connection problem from an event or workflow configuration problem without experimenting on an unsuspecting recipient.
FAQ
Does sending a Loops event send an email?
Not necessarily. Loops describes events as updating contact activity or starting a published workflow. An email may follow if that workflow is configured to send one, but sending the event and sending a transactional template are distinct actions. Check the workflow attached to the event before testing it with a real contact.
Do I need a Loops API key to connect an MCP client?
No API key is needed for the documented Loops MCP OAuth flow. Your client opens Loops in a browser so you can sign in and authorize access. This differs from systems that ask you to paste an API key into a local configuration file; use the Loops connection instructions for your specific client.
Where can I find the Loops MCP server on GitHub?
The connection described by Loops uses its hosted server at https://mcp.loops.so, so you do not need to install a GitHub checkout for that setup. Loops’ MCP page links to client setup guidance. If you are considering a community repository instead, confirm that Loops itself recommends it before granting account access.
Can I test an event without triggering a live workflow?
The event action can start a published workflow, so a test may have real effects if it matches a configured trigger. Use a contact you control and review the workflow’s trigger and actions first. If you only need to confirm the connection, begin with a contact lookup instead of sending an event.
Start free with 1,000 emails a month.