Vaemail

io.github.vaemail

Email infrastructure for AI agents: send, authenticate domains, track delivery, diagnose issues.

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.vaemail-vaemail": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "VAEMAIL_API_KEY": "<secret>",11        "VAEMAIL_BASE_URL": "<value>"12      }13    }14  }15}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

VAEMAIL_API_KEY — VaEmail API key (created in the dashboard, ideally scoped and capped for this agent). Required for every tool except vaemail_capabilities.
VAEMAIL_BASE_URL — API base URL. Default https://app.vaemail.fr.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1VAEMAIL_API_KEY=<secret> VAEMAIL_BASE_URL=<value> claude mcp add io.github.vaemail-vaemail -- npx -y vaemail@1.2.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.vaemail-vaemail": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "VAEMAIL_API_KEY": "<secret>",11        "VAEMAIL_BASE_URL": "<value>"12      }13    }14  }15}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.2.0
API key: VAEMAIL_API_KEY, VAEMAIL_BASE_URL
Last checked: 2026-10-27

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Vaemail?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Vaemail need an API key?

The publisher lists these environment variables: VAEMAIL_API_KEY, VAEMAIL_BASE_URL.

What transport does Vaemail use?

Vaemail runs locally over stdio.

When was Vaemail last checked?

Last checked 2026-10-27. Email infrastructure for AI agents: send, authenticate domains, track delivery, diagnose issues.

From the publisher

Documentation

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

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 [email protected] --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: '[email protected]',
    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: '[email protected]' });
} 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

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/skills
Examples for curl, Node, Python, Claude Code, Codex, OpenAI Agents, LangChain, CrewAI and n8n: https://github.com/vaemail/examples
Registry entry: io.github.vaemail/vaemail (see server.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

Vaemail

io.github.vaemail

Email infrastructure for AI agents: send, authenticate domains, track delivery, diagnose issues.

Communication

Add to Cursor Add to VS Code Run on PlugMCP

GitHub npm Website

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.vaemail-vaemail": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "VAEMAIL_API_KEY": "<secret>",11        "VAEMAIL_BASE_URL": "<value>"12      }13    }14  }15}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

VAEMAIL_API_KEY — VaEmail API key (created in the dashboard, ideally scoped and capped for this agent). Required for every tool except vaemail_capabilities.
VAEMAIL_BASE_URL — API base URL. Default https://app.vaemail.fr.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1VAEMAIL_API_KEY=<secret> VAEMAIL_BASE_URL=<value> claude mcp add io.github.vaemail-vaemail -- npx -y vaemail@1.2.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.vaemail-vaemail": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "VAEMAIL_API_KEY": "<secret>",11        "VAEMAIL_BASE_URL": "<value>"12      }13    }14  }15}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.2.0
API key: VAEMAIL_API_KEY, VAEMAIL_BASE_URL
Last checked: 2026-10-27

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Vaemail?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Vaemail need an API key?

The publisher lists these environment variables: VAEMAIL_API_KEY, VAEMAIL_BASE_URL.

What transport does Vaemail use?

Vaemail runs locally over stdio.

When was Vaemail last checked?

Last checked 2026-10-27. Email infrastructure for AI agents: send, authenticate domains, track delivery, diagnose issues.

From the publisher

Documentation

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 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.

Check everything is wired up:

npx vaemail init

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.

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 [email protected] --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: '[email protected]',
    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: '[email protected]' });
} catch (error) {
  error.code;        // DOMAIN_NOT_VERIFIED
  error.retryable;   // false
  error.pourAgent(); // reason, corrective action, whether to retry
}

Connecter Stripe

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

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/skills
Examples for curl, Node, Python, Claude Code, Codex, OpenAI Agents, LangChain, CrewAI and n8n: https://github.com/vaemail/examples
Registry entry: io.github.vaemail/vaemail (see server.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