Loops helps businesses manage email marketing and customer engagement by organizing contacts and mailing lists, sending transactional emails, tracking events, creating audience segments, and automating workflows through its email marketing platform.
VS Code
Encrypted at rest, isolated from the model
Resolved from an AES-256-GCM vault at the moment of the call and attached to the request — the model never sees the secrets.
Try asking
Return the full schema for one Loops API endpoint: parameters, request body, and responses (refs inlined). Look the endpoint up with search() first, then pass its path and method here to get what execute() needs.
Make an authenticated GET call to the Loops API as the connected user. This tool only reads; it cannot change data or send email. Flow: search() to find an endpoint, describe(path, method) for its schemas, then execute(). Calls run against one team: pass team (an id from the teams tool); if omitted it uses your only team, or returns your teams to choose from. Only endpoints documented in the OpenAPI spec can be called; anything else is rejected. Use execute_write to change data.
Make an authenticated POST, PUT, PATCH, or DELETE call to the Loops API as the connected user. These calls create, update, delete, publish, or send: they take effect immediately, cannot be undone here, and can email real recipients. Only make one the user has asked for. Flow: search() to find an endpoint, describe(path, method) for its schemas, then execute_write(). Calls run against one team: pass team (an id from the teams tool); if omitted it uses your only team, or returns your teams to choose from. Only endpoints documented in the OpenAPI spec can be called; anything else is rejected. Use execute for GET.
Search the Loops API OpenAPI spec for endpoints. Returns a slim listing: method, path, operationId, summary, description, tags. Call describe(path, method) to get the full parameter/request/response schemas for one endpoint before calling execute(). Spec source: https://app.loops.so/openapi.json
List the teams the connected user can run Loops API calls against. Returns id and name for each; pass an id as execute()'s team parameter.
One endpoint, the same key, whichever client you use.
~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)
Replace API_KEY with your own key.
Already have an "mcpServers" section in your config? Just add the server entry inside it.
Discovery, routing, credentials, tool scoping and execution logs all happen at the gateway→connections stay ACTIVE with no work from you
Loops MCP runs through a gateway that holds the credentials, scopes the access and records every call.
Managed auth, hosted MCP servers, and every Loops MCP tool your agent needs.
Free to start.
