Vaemail MCP server

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

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:

id. Only vaemailgetmessage says what became of it. The tool descriptions say so, so an agent does not announce a delivery it cannot know about.

• A send is accepted, not delivered. vaemailsendemail returns 202 and an

the first response for 24 hours instead of sending twice.

• Retries do not duplicate. Pass idempotency_key and a repeat call replays

retryable, and the corrective action with the endpoint that performs it.

• Errors say what to do. Every failure carries a stable code, whether it is

and an allow-list of sender domains. An agent cannot spend more than the key allows.

• Keys are bounded. Scopes, a daily send cap, a cap on recipients per email

result — message bodies excluded. Autonomous, but accountable.

• Every call is logged. Which key, which operation, which parameters, which

whose value still contains a placeholder is flagged publishable: false, because publishing it would break the domain's authentication.

• Human steps are named as such. Publishing DNS records is one. A record

CLI

Shortened. The full README is on GitHub.