Skip to main content
Glama
vaemail

vaemail

Official

VaEmail — email infrastructure for AI agents

Listed on mcpservers.org

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 mcp

Or 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 init

Related MCP server: agentisend

Tools

Tool

What it does

vaemail_preparer_envoi

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.

vaemail_confirmer_envoi

Executes the scheduled or immediate newsletter prepared with the token, after explicit human confirmation. This is destructive.

vaemail_ou_en_est_ma_campagne

Where a campaign stands, in plain sentences: scheduled, sending, sent, opens, clicks.

vaemail_qui_est_abonne

Lists by folder with subscriber counts, or the lists and status of one address.

vaemail_importer_contacts

Adds contacts to a list (created if missing). Never re-subscribes an unsubscribed address.

vaemail_capabilities

What the service supports. No API key needed.

vaemail_send_email

Queue a transactional email, return its id.

vaemail_validate_email

Dry run: would this send go out, and what would block it.

vaemail_get_message

Delivery status and every event for one message.

vaemail_list_messages

Recent messages, filtered by status, tag or recipient.

vaemail_list_domains

Sending domains with live SPF, DKIM and DMARC state.

vaemail_create_domain

Declare a domain, return the DNS records to publish.

vaemail_verify_domain

Re-read the DNS and report what is authenticated.

vaemail_dns_requirements

The records a declared domain still needs.

vaemail_diagnose_deliverability

Why mail is landing badly, with the actions that fix it.

vaemail_list_bounces

Addresses excluded from sending, and why.

vaemail_get_usage

Quota, daily cap on the key, what is left.

vaemail_get_audit_log

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_email returns 202 and an id. Only vaemail_get_message says 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_key and 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 is retryable, 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 stdio

Add --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ée settings.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

invoice.payment_failed

stripe_payment_failed (payment_failed)

customer.subscription.created

stripe_subscription_created (subscription_created)

customer.subscription.deleted

stripe_subscription_deleted (subscription_deleted)

checkout.session.completed

stripe_checkout_completed (checkout_completed)

A Python SDK with the same surface is available: pip install vaemail (https://github.com/vaemail/vaemail-python).

Environment

Variable

Meaning

VAEMAIL_API_KEY

Account API key. Created from the dashboard, under « Clés API ».

VAEMAIL_BASE_URL

API base URL. Defaults to https://app.vaemail.fr.

Also available

Skill and examples

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 tools
vaemail_capabilitiesWhat VaEmail can doA
Read-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?A
Read-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 domainA
Read-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 doneA
Read-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 messageA
Read-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 limitsA
Read-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 sendingA
Read-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 domainsA
Read-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 messagesA
Read-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 sendingA
Read-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 authenticationA
Read-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

    A4.1/5.0

    Scored across 13 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.
      46
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    Appeared in Searches