6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
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
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
mcp. You cannot grant a session that reads contacts but cannot send.execute exposes, which Loops does not enumerate on its MCP page.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.
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.
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.
https://loops.so/docs/mcp-server.md) · retrieved 2026-11-18llms.txt, including the API reference list (retrieved 2026-11-18) · retrieved 2026-11-18initialize to https://mcp.loops.so/ returned 401 with a bearer authentication challenge carrying scope="mcp" and the descriptor https://mcp.loops.so/.well-known/oauth-protected-resource, which names https://app.loops.so as the authorization server (2026-11-18) · retrieved 2026-11-18Connect Loops once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.