How do I get started?

Subscribe, copy your active API Key (which you can generate inside **HiDeliver Portal → Security/Dev Settings**), and connect it. The integration expects standard raw API connections so you interact intuitively through words instead of intricate data schemas.

Can it query active subscriber details globally?

Yes! Direct your AI agent to query list nodes or fetch the comprehensive subscriber logs. The `list_subscribers` action aggregates arrays of real, valid accounts securely for your reporting needs in an instant.

What happens when I want to fetch metrics or fields for one target list?

Provide the exact List ID. The tool evaluates endpoint rules (`get_list`) and unpacks default configuration details (such as names, double-opt rules, and associated status) natively to the terminal.

Can my AI automatically create or append specific subscriber profiles?

Absolutely. Pass specific parameters, including the new email, name, and respective list ID. The system validates the JSON schema instantly with the `create_subscriber` pipeline effectively logging campaigns on the fly.

HiDeliver MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: HiDeliver
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to HiDeliver through the Vinkius — pass the Edge URL in the `mcps` parameter and every HiDeliver 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="HiDeliver Specialist",
    goal="Help users interact with HiDeliver effectively",
    backstory=(
        "You are an expert at leveraging HiDeliver 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 HiDeliver "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 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 HiDeliver MCP Server

Connect your HiDeliver broadcasting account to an AI agent to execute bulk email campaigns directly through conversations.

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

What you can do

Client Lists — Fetch stored customer addresses and list segments immediately to verify delivery rules
Audience Management — Inspect or create subscriber leads straight from within conversational prompts
Campaign Insights — Pull real-time delivery performance lists and broadcast statistics without entering the application

The HiDeliver MCP Server exposes 9 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 HiDeliver to CrewAI via MCP

Follow these steps to integrate the HiDeliver 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 9 tools from HiDeliver

Why Use CrewAI with the HiDeliver MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with HiDeliver 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 the 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

HiDeliver + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries HiDeliver 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 HiDeliver, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain HiDeliver 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 HiDeliver against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

HiDeliver MCP Tools for CrewAI (9)

These 9 tools become available when you connect HiDeliver to CrewAI via MCP:

cancel_delivery

Cancel a mapped delivery trace

create_delivery

Log and schedule a fresh pickup delivery

get_account_balance

Evaluate remaining tokens or cash thresholds

get_delivery

Get parameters surrounding an explicit delivery

get_profile

Get HiDeliver authenticated account logic

get_transaction

Isolate a single API key transaction

list_deliveries

Retrieve active or listed delivery requests

list_transactions

Check global ledger events

update_delivery

Adjust active route parameters

Example Prompts for HiDeliver in CrewAI

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

"Display all the actively loaded marketing lists right now."

"Fetch the underlying metadata and info associated with list ID 55102."

"Add the new email address 'lead@example.com' to list 55301."

Troubleshooting HiDeliver MCP Server with CrewAI

Common issues when connecting HiDeliver 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

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

HiDeliver + CrewAI FAQ

Common questions about integrating HiDeliver 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.