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

Check everything is wired up:

npx vaemail init

Related MCP server: voidmail

Tools

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.

Environment

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