vaemail
OfficialVaEmail MCP server exposes transactional email, domain-authentication, deliverability, suppression, usage, and audit tools.
Check capabilities, limits, scopes, and region without an API key.
Queue a transactional email with HTML/template, subject, tag, reply-to, variables, and idempotency key; get an accepted message id.
Dry-run validate whether a send would go out and identify blockers.
Get one message's delivery status/events or list recent messages filtered by status, tag, or recipient.
List sending domains with live SPF/DKIM/DMARC state.
Declare a domain, return DNS records, verify DNS authentication, and report required DNS records.
Diagnose deliverability with reputation findings and recommended actions.
List bounces/suppressions by reason.
Read quota, daily/key limits, remaining allowance, and audit logs.
VaEmail's outbound mail is sent through Amazon SES in Europe, so the sending, delivery and bounce-reporting capabilities exposed by this server are backed by Amazon SES.
Provides CrewAI example code showing how to wire the VaEmail client into a crew so agents can send transactional and newsletter email and inspect delivery status.
Provides curl examples for the VaEmail API, covering sending messages, checking delivery status, declaring/verifying domains and reading usage.
Provides LangChain example code for calling VaEmail send, validate, message-status and domain tools from a LangChain chain or agent.
Provides n8n workflow examples for triggering VaEmail sends and querying message status, campaign state and domain authentication.
Provides OpenAI Agents example code for invoking VaEmail's send, validate, delivery-tracking and deliverability-diagnosis tools from an OpenAI agent.
An official Python SDK (pip install vaemail) exposing the same surface as the MCP server: send, validate, get message, list messages, domain creation/verification, DNS records, deliverability diagnosis, suppressions, usage and audit logs.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@vaemail Send a transactional email to jane@example.com confirming her order."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VaEmail — email infrastructure for AI agents
MCP server and CLI for VaEmail. Give an agent the ability to send email, authenticate a sending domain, track delivery and diagnose deliverability — without a human reading a dashboard in between.
European infrastructure: servers in Germany, sending through Amazon SES Europe.
Install
# Claude Code
claude mcp add vaemail --env VAEMAIL_API_KEY=swm_your_key -- npx -y vaemail mcp
# Any MCP client
npx -y vaemail mcpOr as a config block:
{
"mcpServers": {
"vaemail": {
"command": "npx",
"args": ["-y", "vaemail", "mcp"],
"env": { "VAEMAIL_API_KEY": "swm_your_key" }
}
}
}GET /api/v1/me identifies the tenant, key prefix, scopes and mode without
returning the secret. Contact operations accept a tenant-unique
external_reference for CRM identifiers and upserts.
Use a sandbox API key for integration tests: reads work normally, while every write
is validated in a transaction that is always rolled back. No row, job, email, SMS,
webhook or outbound HTTP call is emitted, and idempotency keys are not stored.
Sandbox write responses carry X-VaEmail-Sandbox: 1 and sandbox: true in JSON
objects. A sandbox response is never evidence that an email was delivered.
Check everything is wired up:
npx vaemail initRelated MCP server: agentisend
Tools
Tool | What it does |
| Prepares a newsletter draft, resolves the list, optionally sends a test, and returns a recap plus a one-use confirmation token. It never sends or schedules. |
| Executes the scheduled or immediate newsletter prepared with the token, after explicit human confirmation. This is destructive. |
| Where a campaign stands, in plain sentences: scheduled, sending, sent, opens, clicks. |
| Lists by folder with subscriber counts, or the lists and status of one address. |
| Adds contacts to a list (created if missing). Never re-subscribes an unsubscribed address. |
| What the service supports. No API key needed. |
| Queue a transactional email, return its id. |
| Dry run: would this send go out, and what would block it. |
| Delivery status and every event for one message. |
| Recent messages, filtered by status, tag or recipient. |
| Sending domains with live SPF, DKIM and DMARC state. |
| Declare a domain, return the DNS records to publish. |
| Re-read the DNS and report what is authenticated. |
| The records a declared domain still needs. |
| Why mail is landing badly, with the actions that fix it. |
| Addresses excluded from sending, and why. |
| Quota, daily cap on the key, what is left. |
| What this key has done, to report it accurately. |
Both vaemail_confirmer_envoi and vaemail_send_email advertise
destructiveHint: true: sending externally is irreversible. The newsletter confirmation
guard applies to immediate sending; drafts and scheduled campaigns keep their existing behavior.
What this is built to prevent
An agent fails differently from a person. It retries, it does not read a dashboard, and it reports success from a 200. The API is shaped around that:
A send is accepted, not delivered.
vaemail_send_emailreturns 202 and an id. Onlyvaemail_get_messagesays what became of it. The tool descriptions say so, so an agent does not announce a delivery it cannot know about.Retries do not duplicate. Pass
idempotency_keyand a repeat call replays the first response for 24 hours instead of sending twice.Errors say what to do. Every failure carries a stable
code, whether it isretryable, and the corrective action with the endpoint that performs it.Keys are bounded. Scopes, a daily send cap, a cap on recipients per email and an allow-list of sender domains. An agent cannot spend more than the key allows.
Every call is logged. Which key, which operation, which parameters, which result — message bodies excluded. Autonomous, but accountable.
Human steps are named as such. Publishing DNS records is one. A record whose value still contains a placeholder is flagged
publishable: false, because publishing it would break the domain's authentication.
CLI
vaemail init # check config, print the MCP snippet
vaemail capabilities # what the service can do (no key needed)
vaemail send --to a@b.fr --subject Hi --html '<p>Hello</p>'
vaemail status 42 # delivery status of a message
vaemail domains:add exemple.fr # declare a domain, print DNS records
vaemail doctor # why is my email not arriving?
vaemail usage # quota and remaining allowance
vaemail mcp # run the MCP server on stdioAdd --json to any command for machine-readable output.
Use it as a library
The same client the MCP server and the CLI run on is exported, so an application can call VaEmail directly. No dependencies.
import { VaEmail } from 'vaemail';
const client = new VaEmail({ apiKey: process.env.VAEMAIL_API_KEY });
await client.send(
{
to: 'customer@example.com',
subject: 'Your order is on its way',
html: '<p>Tracking number: 1Z999</p>',
},
'order-4711', // idempotency key: safe to replay for 24 hours
);Errors carry what to do next, not just a status code:
try {
await client.send({ to: 'customer@example.com' });
} catch (error) {
error.code; // DOMAIN_NOT_VERIFIED
error.retryable; // false
error.pourAgent(); // reason, corrective action, whether to retry
}Also: capabilities(), health(), validate(), getMessage(),
listMessages(), listDomains(), addDomain(), verifyDomain(),
dnsRecords(), diagnoseDeliverability(), listSuppressions(),
removeSuppression(), usage(), auditLogs().
Connecter Stripe
Utilise une clé Stripe restreinte rk_live_ ou rk_test_, avec Customers en lecture et
Webhook Endpoints en écriture. Une clé secrète sk_ est refusée. VaEmail ne renvoie
aucun secret Stripe : l'état de la connexion expose uniquement les quatre derniers
caractères de la clé et du token du webhook.
Routes REST :
GET /api/v1/integrations/stripe: lire l'état de la connexion ;POST /api/v1/integrations/stripe: créer ou réconcilier le webhook, avec{"api_key":"rk_live_..."}et la portéesettings.write;DELETE /api/v1/integrations/stripe: supprimer le webhook Stripe puis la connexion locale. Action irréversible, à confirmer explicitement par un humain.
Stripe appelle POST /api/v1/webhooks/stripe/{token}. Cette route publique vérifie
Stripe-Signature et ne reçoit pas la clé API VaEmail.
Événements pris en charge et déclencheurs d'automatisation :
Événement Stripe | Déclencheur VaEmail |
|
|
|
|
|
|
|
|
A Python SDK with the same surface is available: pip install vaemail
(https://github.com/vaemail/vaemail-python).
Environment
Variable | Meaning |
| Account API key. Created from the dashboard, under « Clés API ». |
| API base URL. Defaults to |
Also available
OpenAPI specification: https://app.vaemail.fr/openapi.json
Capabilities endpoint: https://app.vaemail.fr/api/v1/capabilities
Agent documentation: https://vaemail.fr/agents
Skill and examples
Agent skill (rules an agent should follow before its first call):
npx skills add vaemail/skills, source https://github.com/vaemail/skillsExamples for curl, Node, Python, Claude Code, Codex, OpenAI Agents, LangChain, CrewAI and n8n: https://github.com/vaemail/examples
Registry entry:
io.github.vaemail/vaemail(seeserver.json)
Dependencies
None. Node 18+ for the built-in fetch, and nothing else — a package an agent
installs on its own should not pull a dependency tree behind it.
License
MIT
Available Tools
13 toolsvaemail_capabilitiesWhat VaEmail can doARead-onlyIdempotent
Return what VaEmail supports: interfaces, capabilities, limits, scopes and region. No API key needed. Call this first when deciding whether VaEmail fits a need.
Inputs: no named parameters.
vaemail_create_domainDeclare a sending domainA
Declare a domain and return the DNS records to add at the registrar, each with what it is for. Declaring a domain does not authenticate it: the records must be published, then verified. Adding DNS records is a human step — report them, do not claim the domain is ready.
Inputs: domain (required), dkim_selector, idempotency_key.
vaemail_diagnose_deliverabilityWhy is my email not arriving?ARead-onlyIdempotent
Diagnose deliverability for the account: authentication of every domain, reputation findings (hard bounces, complaints, where the contacts came from) and recommended actions, each with the endpoint that performs it. Answers "why are my emails from example.com landing badly?" in one call.
Inputs: domain.
vaemail_dns_requirementsDNS records expected for a domainARead-onlyIdempotent
Return the DNS records a declared domain needs, record by record, with the role of each.
Inputs: domain (required).
vaemail_get_audit_logWhat this key has doneARead-onlyIdempotent
Return the log of API actions: which key, which operation, which parameters, which result. Message bodies are never stored in it. Use it to report exactly what was done.
Inputs: limit, since, cursor, operation.
vaemail_get_messageDelivery status of one messageARead-onlyIdempotent
Return the delivery status of a message and every event known about it (delivered, opened, clicked, bounced, complained), plus the transport error when it failed.
Inputs: id (required).
vaemail_get_usageUsage, quota and key limitsARead-onlyIdempotent
Return the monthly quota and what is left of it, today's sends, and for the key in use: its scopes, its daily cap and the remaining allowance. Read it before a batch to know whether to stop.
Inputs: no named parameters.
vaemail_list_bouncesAddresses removed from sendingARead-onlyIdempotent
List addresses excluded from sending: hard bounces, complaints and unsubscribes, with the reason for each. Sending to one of them is refused, so read this before retrying a failed recipient.
Inputs: limit, since, cursor, reason.
vaemail_list_domainsList sending domainsARead-onlyIdempotent
List the sending domains of the account with the live state of their SPF, DKIM and DMARC records.
Inputs: no named parameters.
vaemail_list_messagesList recent messagesARead-onlyIdempotent
List messages newest first, filtered by status, tag or recipient. Paginate with the returned next_cursor.
Inputs: to, tag, limit, cursor, +1 more.
vaemail_send_emailSend an emailA
Queue a transactional email and return its id. The call returns as soon as the message is ACCEPTED, not when it is delivered: use vaemail_get_message to find out what happened to it. Pass idempotency_key when retrying so a network timeout cannot send the same message twice.
Inputs: to (required), tag, html, subject, +5 more.
vaemail_validate_emailCheck a send without sendingARead-onlyIdempotent
Dry run: report whether the email would go out, and name what would block it. Sends nothing. Use it right after setup, before the first real message.
Inputs: to (required), html, subject, template_id.
vaemail_verify_domainVerify domain authenticationARead-onlyIdempotent
Read SPF, DKIM and DMARC for a domain in the public DNS and report each record. Without SPF and DMARC, large mailbox providers file the mail as spam.
Inputs: domain (required), dkim_selector.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Most tools target a distinct resource and action: send, validate, get message, list messages, bounces, usage, audit, domains. The only mild overlap is between vaemail_dns_requirements and vaemail_create_domain, since both return DNS records, but they are separated by stage: one is a general reference and the other acts on a specific newly declared domain.
All tools share the vaemail_ prefix and most follow a clear verb_noun pattern such as list_domains, send_email, get_message, create_domain. Two tools, vaemail_capabilities and vaemail_dns_requirements, are noun-only rather than verb_noun, which is a minor deviation but does not create confusion.
13 tools is well within the ideal range and appropriate for a transactional email service. Each tool covers a meaningful part of the workflow: capabilities, domain setup, sending, delivery tracking, bounce management, validation, usage, and diagnostics.
The tool surface covers the main transactional email lifecycle: send, validate, track, list, diagnose deliverability, manage domain verification, and review bounces. Minor gaps exist such as no domain removal or bounce management beyond listing, but agents can complete core workflows without dead ends.
Maintenance
Related MCP Connectors
Send email, manage domains, templates, webhooks and broadcasts from your AI agent.
Send email, manage domains, templates, webhooks and broadcasts from your AI agent.
Transactional email for AI agents: templates, domain verify, and sends.
Email for AI agents: send from your verified domain, track delivery, list mail, validate addresses.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously create email accounts, verify domains, send and receive emails, and monitor delivery events without requiring human sign-up or payment.1-
- AlicenseAqualityBmaintenanceEnables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.46MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to work with real email: add domains with exact DNS records, create mailboxes, aliases and catch-alls, read one unified inbox across them, wait for sign-up codes and magic links, then send, reply in-thread, forward and draft. Scoped tokens with a send permission and daily cap, dry runs on every write, signed webhooks and a full audit log keep agent mail controlled.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables sending transactional emails individually or in batches, checking delivery status, and monitoring domain email reputation metrics. It supports email tracking with tags and custom metadata.MIT