Loops

Manage Loops contacts, send events and transactional email from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Loops connector does

The Loops MCP server connects the Loops email platform to Claude. Through four gateway tools it reaches the Loops API: find and update contacts, manage mailing lists, send events that start workflows, send transactional email, and work on campaigns and email content. Sending is real. Sign-in is OAuth with your Loops account, under a single scope.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Loops tools (4)

  • describe
  • execute
  • search
  • teams

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • One scope, no read-only mode. The descriptor advertises only mcp. You cannot grant a session that reads contacts but cannot send.
  • The surface is the API, not four tools. The real reach depends on which Loops API operations execute exposes, which Loops does not enumerate on its MCP page.
  • CIMD-only clients. A client that relies on dynamic client registration or a pasted client ID cannot connect, per Loops' troubleshooting.
  • Amp CLI is unsupported. Loops says the Amp CLI cannot add the server yet.
  • Published is the documented gate, and the API can publish. Loops describes the transactional send and the workflow trigger as working on published items. Its API reference also lists publishing a transactional draft and sending a test preview, so publishing is not a barrier an agent cannot cross.
  • We could not read tool schemas or annotations. The endpoint returned 401 to an anonymous request. Tool names come from Anthropic's directory; their behaviour comes from Loops' docs.

Frequently asked questions

Why does my client ask for a Loops client ID or secret?

Because the client is not using Client ID Metadata Documents. Loops identifies MCP clients through CIMD, so the client supplies its own ID at sign-in and Loops has no client ID or secret to give you. A prompt for one, or an error saying dynamic registration was rejected, means you should update the client or use one Loops documents, such as Claude, ChatGPT, Codex CLI or VS Code 1.106.

What should I do if the Loops sign-in fails?

Remove the server and add it again. Loops' troubleshooting steps are to delete the Loops server from your client, add https://mcp.loops.so again, complete the browser sign-in and authorise access, then ask which Loops teams you belong to. If it still fails, contact Loops support with your client name, client version and the exact error message, which is what Loops asks for.

Can the Loops connector send email to my contacts?

Yes. Loops documents that the connector can send a published transactional email with data variables, and send events that start published workflows, which can themselves send email. Both reach real recipients. Loops' docs also list creating and managing campaigns. Keep your client's tool approval on for the execute tool, because the single mcp scope does not separate reading from sending.

Sources

Use it in an agent

Put Loops to work.

Connect Loops once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.