servers / loops-so-docs-mcp-server

Loops MCP server

officialstreamable_httpremoteofficialhealthy

Email marketing MCP for SaaS — contacts, campaigns, workflows

Official hosted Loops MCP for email marketing workflows — manage contacts, campaigns, transactional email, and workflows via OAuth over Streamable HTTP at mcp.loops.so.


00About

Loops is the official hosted MCP server for the Loops email platform (marketing, lifecycle, and transactional email for SaaS). Connect at https://mcp.loops.so over Streamable HTTP with OAuth — no local package to install. Instead of one tool per REST endpoint, the server exposes four meta-tools (teams, search, describe, execute) that discover and run Loops API operations at runtime across contacts, mailing lists, events, campaigns, transactional email, workflows, and the rest of the public API.

Hosted OAuth MCP

Remote Streamable HTTP at mcp.loops.so with browser OAuth (scope mcp). Works with Claude, ChatGPT, Codex, OpenCode, and Amp.

Meta-tools over the full API

search / describe / execute dispatch to Loops REST operations (contacts, campaigns, transactional, workflows, and more) instead of shipping dozens of fixed tools.

Team-scoped access

teams lists the Loops workspaces you can access; execute runs operations for a chosen team.

Agent-ready email ops

Manage contacts, send transactional email, audit workflows, and operate campaigns from the agent loop.

Who it’s for. SaaS teams and agents that need to operate Loops email — contacts, campaigns, transactional sends, and workflows — without leaving the MCP client.

Example prompts

List teams
Which Loops teams am I a part of?
Find then send
Search for the operation to send a transactional email, describe its request shape, then execute it for our primary team with a test recipient.
Workflow audit
List workflows for my team, then describe how to update a workflow node that filters churn-risk contacts.

auth: OAuth (scope mcp) via browser sign-in · pricing: Included with Loops — no extra MCP fee · reviewed by MCPExplorer


01Tools · 4

How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.

ToolRiskSide effectsApproval
describe
Inspect the request shape of a Loops API operation before calling it.
readfalseunknown
execute
Run a Loops API operation for a chosen team — dynamic dispatch over the Loops REST API (contacts, mailing lists, events, campaigns, transactional email, workflows, and more).
writetrueunknown
search
Find the right Loops API operation for a task (contacts, campaigns, transactional email, workflows, and the rest of the Loops REST surface).
writetrueunknown
teams
List the Loops teams the authenticated user can access.
readfalseunknown

02Install & source
https://mcp.loops.so
remote_url

03Access granted
mcpoauth

The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.


05Provenance & freshness
sourcesUser submissions [p7]
last_checked2026-09-23 16:31Z
next_check2026-09-25 09:40Z
cadenceevery 48h
verifiedhandshake:skipped tools_list:passed metadata:passed
index_statusindex5 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README. Loops MCP — as seen on mcpexplorer.com

[![Loops MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/loops-so-docs-mcp-server.svg)](https://mcpexplorer.com/servers/loops-so-docs-mcp-server)

Next step

This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.

Explore loadouts →