Bring Gdpr Compliant
to LlamaIndex
Learn how to connect Mailingwork to LlamaIndex and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Mailingwork MCP Server?
Connect your Mailingwork account to any AI agent and manage email campaigns through natural conversation.
What you can do
- Campaign Management — Create, schedule, and track email campaigns
- Subscriber Lists — Manage mailing lists with import and segmentation
- Report Analytics — Access open rates, click maps, and delivery metrics
- Deliverability — Monitor bounce rates and sender reputation
- Template Management — Browse and manage email templates
How it works
1. Subscribe to this server
2. Enter your Mailingwork username and password
3. Start managing campaigns from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Email Marketers — run campaigns with detailed analytics
- German Businesses — GDPR-compliant email marketing
- Agencies — manage multi-client email programs
Built-in capabilities (10)
Create a new subscriber
Get mailing details
Get subscriber details
List all subscriber lists
List all mailings/campaigns
List all subscribers
List all tags
g., order confirmation). Send a transactional email
Trigger an automated workflow
Update an existing subscriber
Why LlamaIndex?
LlamaIndex agents combine Mailingwork tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Mailingwork tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Mailingwork tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Mailingwork, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Mailingwork tools were called, what data was returned, and how it influenced the final answer
Mailingwork in LlamaIndex
Mailingwork and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mailingwork to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Mailingwork in LlamaIndex
The Mailingwork 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Mailingwork for LlamaIndex
Every tool call from LlamaIndex to the Mailingwork MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I manage campaigns and track delivery?
Yes. Create and schedule campaigns, track opens, clicks, bounces, and monitor sender reputation.
Does Mailingwork use Basic Auth?
Yes. Mailingwork uses HTTP Basic Auth with username and password against api.mailingwork.de/webservice/v2.
Is Mailingwork GDPR-compliant?
Yes. Mailingwork is a German email platform built for GDPR compliance with data processing in EU data centers.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Mailingwork tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp