How do I get a Loops API key?

Log in to your Loops account, go to **Settings** → **API**, and generate a new API key. Ensure it has the necessary permissions. Then provide it when prompted by the MCP server setup.

What operations are supported by this MCP server?

The server supports: testing API key validity, finding/creating/updating/deleting contacts, listing mailing lists, sending events to trigger email journeys, sending transactional emails, listing sent transactional emails, and checking contact suppression status.

What is the difference between mailing lists and transactional emails in Loops?

Mailing lists are used for marketing campaigns and automated email journeys. Transactional emails are one-off, triggered messages like receipts, password resets, or order confirmations. Both are supported by this MCP server.

How can I check if an email is suppressed in Loops?

Use the 'get_contact_suppression' tool provided by this MCP server. Simply ask the AI to check the suppression status for any email address, and it will tell you if that email is currently suppressed from receiving emails.

Loops MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Loops
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Loops through Vinkius, pass the Edge URL in the `mcps` parameter and every Loops tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Loops Specialist",
    goal="Help users interact with Loops effectively",
    backstory=(
        "You are an expert at leveraging Loops tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Loops "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Loops MCP Server

Loops is a modern email marketing and transactional email platform designed for startups and growing businesses. It provides powerful automation for email journeys, audience segmentation, contact management, and detailed analytics. This MCP server enables AI agents to manage contacts, mailing lists, trigger events for automated journeys, send transactional emails, and check suppression statuses — all through natural language commands.

When paired with CrewAI, Loops becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Loops tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

Key capabilities:

Search, create, update, and delete contacts

Manage mailing lists

Trigger email journeys with events

Send transactional emails programmatically

Check email suppression status

View sent transactional email history

The Loops MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Loops to CrewAI via MCP

Follow these steps to integrate the Loops MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Loops

Why Use CrewAI with the Loops MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Loops through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Loops + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Loops MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Loops for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Loops, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Loops tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Loops against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Loops MCP Tools for CrewAI (10)

These 10 tools become available when you connect Loops to CrewAI via MCP:

create_contact

Requires an email address. Optionally accepts firstName, lastName, and userGroup. Create a new contact in Loops

delete_contact

This action cannot be undone. Delete a contact from Loops by ID

find_contact

Returns the contact details if found. Find a contact in Loops by email address

get_contact_suppression

Suppressed emails will not receive emails. Returns the suppression status for the given email. Check if an email address is suppressed in Loops

list_mailing_lists

Use this to discover available lists for subscribing contacts. List all mailing lists in Loops

list_transactional_emails

Optionally accepts a limit parameter to control the number of results returned. List recently sent transactional emails from Loops

send_event

Requires an eventName. Optionally accepts email and/or userId to identify the recipient. Send an event to trigger email journeys in Loops

send_transactional_email

Requires the transactionalId. Optionally accepts email and dataVariables (as JSON string) for template variables. Send a transactional email via Loops

test_api_key

Returns success/failure status. Test if the Loops API key is valid and working

update_contact

Requires the contact ID. Accepts any fields to update such as firstName, lastName, email, userGroup, etc. Update an existing contact in Loops by ID

Example Prompts for Loops in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Loops immediately.

"Find the contact with email user@example.com in Loops"

"Create a new contact in Loops with email newuser@example.com, first name John, and last name Doe"

"List all mailing lists in my Loops account"

"Send a transactional email with template txn_123 to customer@example.com"

Troubleshooting Loops MCP Server with CrewAI

Common issues when connecting Loops to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Loops + CrewAI FAQ

Common questions about integrating Loops MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.