MCP
Loops MCP server: email reports and sends in Claude, Codex or Cursor
TL;DR
Loops reaches Claude, Codex or Cursor through the Agent Planners MCP endpoint with 14 reads and 6 writes. Property updates follow the key's write mode; sending email, adding or subscribing a contact and deleting one are held for a person on every key mode.
What this setup adds
| Calling Loops' API yourself | Agent Planners MCP | |
|---|---|---|
| Sign-in | Your API key in each client | One key pasted on the Loops card, stored encrypted |
| People | Full contact records | Masked: first letter + domain of an email, no names or custom values |
| Sending | Whatever you send | Held for a person; checked first; one idempotency key per send |
| Other platforms | Loops only | Your ads, analytics and CRM on the same endpoint |
How to configure it
- 1Connect Loops with an API key on its card on Integrations.
- 2Create a key in API & MCP:
tools:readfor reading, addtools:writefor changes. To keep a key to Loops, choose Only these platforms → Loops. - 3Add the server to your client, run
describe_permissions, thenloops__get_account.
Every client's setup, including OAuth sign-in without a key: MCP setup guide.
The Loops tools
| Tool | Kind | What it does |
|---|---|---|
loops__get | Read | ANY Loops read by path (GET): api-key, lists, contacts/properties, campaigns[/{id}[/metrics]], campaign-groups, audience-segments[/{id}], transactional-emails[/{id}[/metrics]], transactional-groups, event-patterns[/{i… |
loops__get_account | Read | The Loops team the key belongs to (GET /v1/api-key): teamName, and the rate limit Loops reported. |
loops__list_mailing_lists | Read | Mailing lists (GET /v1/lists): id, name, description, isPublic. |
loops__list_contact_properties | Read | Contact properties (GET /v1/contacts/properties): key, label, type (string | number | boolean | date). customOnly:true = only the team's custom ones. |
loops__find_contact | Read | Find ONE contact by email or userId (GET /v1/contacts/find): found, id, the email masked, source, subscribed, userGroup, userId, mailing lists, optInStatus, which custom properties are set (names only). |
loops__check_suppression | Read | Is a contact suppressed (bounces / complaints stop all sending) and how many suppression removals are left this 30-day period (GET /v1/contacts/suppression). |
loops__list_campaigns | Read | Campaigns (GET /v1/campaigns, cursor pages of ≤ 50): id, name, status (Draft | Scheduled | Sending | Sent), mailing list / audience segment, scheduling, app link. |
loops__get_campaign_metrics | Read | ONE sent campaign's all-time numbers (GET /v1/campaigns/{id}/metrics): sends, opens, clicks, unsubscribes, spamReports, hardBounces, softBounces — opens / clicks count a send once — plus open / click / unsubscribe / b… |
loops__campaign_report | Read | Every SENT campaign with its metrics in one table (list + one metrics read each, ≤ 50 campaigns): sends, opens, clicks, rates, unsubscribes, bounces, spam reports, newest first. |
loops__list_audience_segments | Read | Audience segments (GET /v1/audience-segments): id, name, description, filter (match all | any + conditions). |
loops__list_transactional_emails | Read | Transactional emails (GET /v1/transactional-emails): id, name, published or draft only, the data variables the published version needs, group, app link. |
loops__get_transactional_email_metrics | Read | ONE transactional email's all-time numbers across its published versions (GET /v1/transactional-emails/{id}/metrics): sends, deliveries, spamReports, hardBounces, softBounces + delivery rate. |
loops__list_workflows | Read | Workflows (GET /v1/workflows; Loops' automations — the 'loops'): id, name, group, created / updated, app link. |
loops__list_event_patterns | Read | Events Loops has received (GET /v1/event-patterns): eventName, the platform an incoming webhook sends it from. |
loops__create_contact | Write — a person decides | Create a contact (POST /v1/contacts/create): { accountId?, email, firstName?, lastName?, userId?, userGroup?, source?, subscribed? (default true), mailingLists? ({ listId: true }), properties? ({ key: value } — the pr… |
loops__update_contact | Write — a person decides | Change a contact found by email or userId (PUT /v1/contacts/update — Loops CREATES the contact when none matches, so this tool reads first and refuses an unknown contact unless createIfMissing:true): { accountId?, ema… |
loops__delete_contact | Write — a person decides | Delete ONE contact by email or userId (POST /v1/contacts/delete). |
loops__create_contact_property | Write | Create a custom contact property (POST /v1/contacts/properties): { accountId?, name (camelCase, e.g. planName), type: string | number | boolean | date }. |
loops__send_event | Write — a person decides | Send an event for a contact (POST /v1/events/send, Idempotency-Key sent): { accountId?, email? | userId?, eventName, eventProperties?, mailingLists?, properties? (contact properties to update), dryRun?, idempotencyKey… |
loops__send_transactional_email | Write — a person decides | Send a published transactional email (POST /v1/transactional, Idempotency-Key sent): { accountId?, transactionalId, email, dataVariables? ({ name: value } — every variable the published email uses is required), addToA… |
What waits for a person, whatever the key allows
- Sending a transactional email and sending an event (an event can start a workflow that emails the contact) — unless it is a dry run, which checks the send and sends nothing.
- Creating a contact (a new contact is subscribed and can start a "contact added" workflow), subscribing one or adding one to a mailing list.
- Deleting a contact (it cannot be undone).
Tested live on a real Loops team (2026-11-17): every read, and a test contact created, changed, looked up (masked) and deleted. Sends were dry runs only — nothing was emailed. Loops setup guide · Loops platform page · Loops MCP server
Frequently asked questions
- How do I connect Claude to Loops?
- Paste a Loops API key (Settings → API) on the Loops card on Integrations, create an Agent Planners key in API & MCP, add the MCP server to Claude and call loops__get_account.
- Can an MCP client send email through Loops on its own?
- No. Sending a transactional email or an event is held for a person on every key mode; a dry run sends nothing.