Loops MCP Server

Loops is a modern email platform for SaaS companies, used to send product, marketing, and transactional email. As of May 2026, Loops itself has not shipped a first-party MCP server (their "Email for agents" page lists "MCP server" as Coming Soon), but the Loops REST API is exposed as an MCP toolkit through several hosted MCP gateways including Composio, Pipedream, and Zapier MCP.

These gateways wrap the public Loops REST API and expose its operations as MCP tools: creating, finding, updating, and deleting contacts; managing contact properties; listing mailing lists; sending events that trigger Loops automations; and sending or listing transactional emails. Authentication is handled by the gateway using your Loops API key (generated in the Loops dashboard under Settings, API).

Until an official Loops MCP server ships, Composio's hosted Loops toolkit is the most fully documented option, with 12 actions covering the entire Loops API surface. The Loops team has also shipped supporting tooling for AI agents in the meantime: a CLI (Loops-so/cli), installable agent skills (Loops-so/skills), and official SDKs for JavaScript, Nuxt, PHP, and Ruby.

Tools

Status

There is no official first-party Loops MCP server yet. The Loops "Email for agents" page lists an MCP server as "Coming Soon." In the meantime, the Loops API can be accessed through hosted MCP gateways.

Prerequisites

• A Loops account with an API key (Dashboard, Settings, API, Generate key)
• An account on one of the MCP gateway providers below

Option A: Composio (recommended, most complete)

1. Create a Composio account at https://dashboard.composio.dev
2. Connect the Loops.so toolkit and paste your Loops API key when prompted
3. Create a Tool Router or MCP session and copy the generated URL
4. Add the MCP server to your client:

{
  "mcpServers": {
    "loops": {
      "url": "https://mcp.composio.dev/<your-session-id>",
      "headers": {
        "x-composio-api-key": "<YOUR_COMPOSIO_API_KEY>"
      }
    }
  }
}

Option B: Pipedream Connect

The Pipedream MCP endpoint is a single static URL. Authentication is performed when the server is configured in your app.

{
  "mcpServers": {
    "loops": {
      "url": "https://mcp.pipedream.net/v2",
      "headers": {
        "Authorization": "Bearer <PIPEDREAM_TOKEN>"
      }
    }
  }
}

See https://mcp.pipedream.com/app/loops_so for the per-client setup guide.

Option C: Zapier MCP

Go to https://zapier.com/mcp/loops, connect your Loops account, and copy the generated MCP URL into your client config.

Until the official server ships

For terminal or skill-based workflows, Loops ships an official CLI and a skills repo for Claude Code, Codex, and Cursor:

# CLI
brew install Loops-so/tap/loops
loops auth login

# Agent skills
npx skills add https://github.com/Loops-so/skills --global

• Auto-create or update a Loops contact when a new user signs up, syncing user properties from a database or CRM
• Trigger a Loops event (e.g. trial_started, payment_failed) from an agent workflow so the matching automation loop fires
• Send transactional emails (password resets, receipts, magic links) by invoking a Loops template from natural language
• Audit a contact: look up by email, list properties, and decide whether to update segmentation or unsubscribe
• Inspect transactional templates and mailing lists during onboarding so an agent can wire up a new product email flow

• "Create a Loops contact for alex@acme.com, set firstName Alex, userGroup Pro, and subscribed true."
• "Send the welcome_v2 transactional email to alex@acme.com with the variable firstName set to Alex."
• "Send a trial_started event for user_id 1234 with eventProperty plan=team."
• "Find the Loops contact for jordan@example.com and update their lifecycleStage to customer."
• "List all transactional email templates in our Loops workspace so I can pick the right one."

• Covers the full Loops public API surface (contacts, properties, events, transactional emails, mailing lists) through Composio
• No code to maintain: the MCP gateway handles auth, retries, and rate limiting
• Works with any MCP-capable client (Claude Desktop, Cursor, Claude Code, Codex, Windsurf)
• Loops also ships an official CLI and agent skills repo that complement the MCP workflow

• No official first-party Loops MCP server yet; you depend on a third-party gateway (Composio, Pipedream, or Zapier)
• Tool names, parameter shapes, and rate limits vary across gateways and may change as Loops releases its own server
• The Loops API enforces a baseline 10 requests/second/team limit, which applies regardless of the gateway used

• Resend MCP: similar transactional-first email API with community MCP servers
• Postmark MCP: another transactional email provider available through Composio/Pipedream toolkits
• Loops CLI + skills: for agents that prefer shell commands over MCP tools, Loops-so/cli and Loops-so/skills cover the same operations