Loops MCP Server: How It Works, What It Can Do and an Alternative

Short answer: yes, Loops has an official MCP server. It's hosted at https://mcp.loops.so, you sign in with OAuth, and it's listed in Claude's connector directory. It's also available as a ChatGPT plugin and in OpenAI's Codex. Instead of one tool per feature, it gives your assistant four general tools that can call almost any part of the Loops API.

It's a good fit for SaaS developers who want contacts, events and transactional email at hand in Claude Code. It's more limited for marketing campaigns, which you still send from the Loops dashboard. This guide covers how it works and where it stops, as of October 2026.

We run Audienceful, an email marketing platform with its own MCP server, so weigh our view accordingly. We've kept the Loops sections to what Loops documents.

How the Loops MCP server works

MCP (Model Context Protocol) is the open standard AI assistants use to work with outside tools. Most MCP servers expose a long list of named tools. Loops takes a different approach and exposes four:

• search finds the right Loops API operation for what you asked.
• describe shows the assistant what that operation expects.
• execute runs it for a chosen team.
• teams lists the Loops teams you can access.

The upside is a small, tidy tool list that keeps up with the API automatically. The downside is that the assistant has to work out the API call each time, so it's less obvious from the tool list what it will actually do.

What it can do

Through those four tools, your assistant can reach most of the Loops API:

• Contacts and properties: find, add and update contacts and their custom properties.
• Mailing lists: add people to or remove them from lists.
• Events: send events, which update contacts and can start published workflows. (Loops renamed its "loops" to workflows in May 2026, so older guides use the old name.)
• Transactional email: send a published transactional template with your data variables.
• Draft campaigns: since Loops' Content API launched in June 2026, campaigns can be created and edited as drafts through the API.

Loops' own guide says to review and send campaigns from the dashboard. We couldn't find an API operation that sends a campaign, so expect your assistant to stop at a draft.

How to set it up

Claude (web or desktop): open Settings → Connectors, browse for Loops and click Connect.

Claude Code:

claude mcp add loops https://mcp.loops.so --scope user --transport http

Then run /mcp, choose Loops and sign in.

Codex:

codex mcp add loops --url https://mcp.loops.so

ChatGPT: install the Loops plugin from the plugin directory.

To check it's working, ask: "Which Loops teams am I a part of?"

Where it stops

• Campaigns end as drafts. You can have the assistant write and lay out a campaign, but someone still opens the dashboard to send it.
• Workflows are limited through the API. Some workflow endpoints are still labelled alpha and need to be enabled for your team.
• There's no step that previews recipients. For transactional sends and contact changes, the safety net is your AI client's tool-approval prompt. Loops hasn't documented OAuth scopes either, so plan on giving the assistant full account access.
• Hosted only. There's no local version, which most people won't miss.

Loops MCP vs Audienceful MCP

Switching from Loops?

• Pay less on a small list. At 3,000 contacts Audienceful is $29/mo billed yearly ($37.50 monthly), against $49 for Loops. See the full Loops comparison.
• Campaigns that leave the chat. Your assistant can schedule the send after you approve the recipients, instead of stopping at a draft.
• Product and marketing email together. Transactional email from your app or the chat, using the same contacts, emails and reporting as your campaigns.
• An AI agent built in, too. The same work happens inside Audienceful with the built-in agent, so you're not tied to one assistant. Both are on every plan, and the MCP server doesn't use AI credits.

Start free: the free plan covers up to 1,000 contacts. Then bring your list over with our migration guide.

When to use which

Loops is a good choice if a developer owns your email, your campaigns are occasional, and you mostly want the assistant to manage contacts and fire events. Its free plan covers up to 4,000 emails a month to your 1,000 newest contacts, transactional and marketing combined. Check Loops' pricing for paid tiers.

Audienceful is the better fit if you want the assistant to finish the job. It can write the onboarding sequence, build the "trial users who haven't connected an integration" audience, schedule the product-update campaign, and tell you which link got the most clicks afterwards, all from one conversation. Nothing sends until you approve the exact recipients, and new automations start paused. Product email works too: your app sends transactional email with one API call, your assistant can send one from chat, and the same events can start marketing sequences.

If you're comparing platforms more broadly, see Loops vs Audienceful and our guide to email marketing for SaaS. To try it, connect Claude Code or Cursor or Claude to Audienceful. It's free on every plan.

FAQs

Does Loops have an MCP server?

Yes. Loops hosts an official MCP server at https://mcp.loops.so. It's listed in Claude's connector directory and is also available for ChatGPT and Codex.

Can the Loops MCP server send campaigns?

It can create and edit draft campaigns. According to Loops' documentation, sending happens from the Loops dashboard.

Do I need an API key for the Loops MCP server?

No. Supported clients open Loops in your browser so you can sign in and authorize access.

What's the best Loops MCP alternative?

For SaaS teams that want an assistant to handle the whole job, from writing and audiences to automations, sends and reports, Audienceful's email marketing MCP server is included on every plan and requires your approval before any send.