Send a transactional email

Send a transactional email

Sends a published transactional email to one recipient, filled with the data variables you pass.

Note: Send an Idempotency-Key header so a retry never sends twice. Attachments work only after Loops support enables them.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "loops": { "url": "https://mcp.loops.so" } } }

Call the MCP tool execute with POST /v1/transactional.

Server URL: https://mcp.loops.so

Note: Every operation runs through three tools: search finds it, describe shows its inputs, execute runs it.

CLI (official)

Install the command, then confirm it runs.

brew install loops-so/tap/loops
loops --version

Run loops transactional send.

Set $LOOPS_API_KEY in your environment first (get a key: https://app.loops.so/settings?page=api).

API (official)

• Base URL: https://app.loops.so/api
• Endpoint: POST /v1/transactional
• Auth: send the header Authorization: Bearer $LOOPS_API_KEY
• Get a key: https://app.loops.so/settings?page=api
• Docs: https://loops.so/docs/api-reference/intro

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.