Skip to content

Loops MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

Manage Loops contacts, mailing lists, and transactional/event emails.

Deletes · 6Changes · 1
CompareRegistry entry

10 tools: 6 can delete or cancel things, 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http loops https://loops.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

10 tools

Deletes or cancels 6Claude Code: deny
  • loops_create_contactCreates a contact in Loops (additive).No findings

    Why it is in this group

    • The name "loops_create_contact" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Creates a contact in Loops (additive). Loops API: POST /v1/contacts/create.

    Annotations the server declares

    • title: Create a contact
    • destructiveHint: true
  • loops_create_contact_propertyCreates a custom contact property/field (additive schema change).No findings

    Why it is in this group

    • The name "loops_create_contact_property" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Creates a custom contact property/field (additive schema change). Loops API: POST /v1/contacts/properties.

    Annotations the server declares

    • title: Create a contact property
    • destructiveHint: true
  • loops_delete_contactDeletes a contact from Loops.No findings

    Why it is in this group

    • The name "loops_delete_contact" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Deletes a contact from Loops. Destructive. Supply email OR userId. Loops API: POST /v1/contacts/delete.

    Annotations the server declares

    • title: Delete a contact
    • destructiveHint: true
  • loops_send_eventSends an event to Loops for a contact — TRIGGERS any automations/loops subscribed to this event.No findings

    Why it is in this group

    • The name "loops_send_event" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Sends an event to Loops for a contact — TRIGGERS any automations/loops subscribed to this event. Loops API: POST /v1/events/send.

    Annotations the server declares

    • title: Send an event
    • destructiveHint: true
  • loops_send_transactionalSENDS a real transactional email via a Loops template.No findings

    Why it is in this group

    • The name "loops_send_transactional" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    SENDS a real transactional email via a Loops template. This dispatches an actual email to the recipient. Loops API: POST /v1/transactional.

    Annotations the server declares

    • title: Send a transactional email
    • destructiveHint: true
  • loops_update_contactUpdates (or creates) a contact by email/userId.No findings

    Why it is in this group

    • The name "loops_update_contact" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Updates (or creates) a contact by email/userId. Upserts — creates the contact if not found. Loops API: PUT /v1/contacts/update.

    Annotations the server declares

    • title: Update a contact
    • destructiveHint: true
Changes things 1Claude Code: ask
  • loops_test_api_keyVerify the configured Loops API key and return the team name — a good first call.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify the configured Loops API key and return the team name — a good first call. Loops API: GET /v1/api-key.

    Annotations the server declares

    • title: Test API key
    • readOnlyHint: true
Only reads 3Claude Code: allow
  • loops_find_contactFind a contact by email or userId (supply at least one).No findings

    Why it is in this group

    • The name "loops_find_contact" says "find": a word for reading.
    Description, as the server wrote it
    Find a contact by email or userId (supply at least one). Loops API: GET /v1/contacts/find.

    Annotations the server declares

    • title: Find a contact
    • readOnlyHint: true
  • loops_list_contact_propertiesList contact fields / custom properties defined in Loops.No findings

    Why it is in this group

    • The name "loops_list_contact_properties" says "list": a word for reading.
    Description, as the server wrote it
    List contact fields / custom properties defined in Loops. Loops API: GET /v1/contacts/properties.

    Annotations the server declares

    • title: List contact properties
    • readOnlyHint: true
  • loops_list_mailing_listsList all mailing lists in the Loops account (id + name).No findings

    Why it is in this group

    • The name "loops_list_mailing_lists" says "list": a word for reading.
    Description, as the server wrote it
    List all mailing lists in the Loops account (id + name). Loops API: GET /v1/lists.

    Annotations the server declares

    • title: List mailing lists
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http loops https://loops.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__loops__loops_find_contact",
      "mcp__loops__loops_list_contact_properties",
      "mcp__loops__loops_list_mailing_lists"
    ],
    "ask": [
      "mcp__loops__loops_test_api_key"
    ],
    "deny": [
      "mcp__loops__loops_create_contact",
      "mcp__loops__loops_update_contact",
      "mcp__loops__loops_delete_contact",
      "mcp__loops__loops_create_contact_property",
      "mcp__loops__loops_send_event",
      "mcp__loops__loops_send_transactional"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as loops. Review it before you use it.