Skip to content

Summary

Official MailPace MCP server: send transactional email, check delivery and bounce status, and manage sending domains and API tokens, with an optional recipient allowlist and idempotent sends.

Features

  • Send transactional email with attachments, tags and idempotency keys
  • Delivery, bounce and deferral status lookups
  • Create, update and DNS-verify sending domains
  • Create, rename and revoke domain API tokens
  • Recipient allowlist to block unexpected sends
  • Tokens from environment only; Docker image runs as non-root

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "MailPace MCP" tools will be available.
{
  "mcpServers": {
    "mailpace-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mailpace/mcp"
      ],
      "env": {
        "MAILPACE_API_TOKEN": "your-domain-api-token",
        "MAILPACE_ORGANIZATION_TOKEN": "your-organization-api-token"
      }
    }
  }
}

Description

MailPace MCP exposes MailPace — a transactional email provider — to MCP clients: sending messages, checking what happened to them, and managing the domains and tokens behind them. It is a TypeScript stdio server published on npm as @mailpace/mcp.

Tools

With a domain API token the agent can send email (mailpace_send_email, with attachments, tags and an Idempotency-Key) and look up delivery, bounce or deferral status for a message. With an organization API token it can list, create, update and verify domains (checking DKIM and advanced verification DNS records) and list, create, rename or revoke domain API tokens. Tools are registered according to which tokens are present, and each declares structured output schemas and MCP behaviour annotations.

Guardrails

Sending email is a side effect an agent should not take lightly, and the server has two controls for it. MAILPACE_ALLOWED_RECIPIENTS takes a comma-separated allowlist of addresses or @domain rules, and sends to anyone else are refused — recommended for unattended use and against prompt injection. Idempotency keys stop a retried send from delivering twice. Credentials are read only from environment variables, never command-line arguments, so they do not appear in process listings.

Running it

Requires Node.js 20+. Run npx -y @mailpace/mcp with MAILPACE_API_TOKEN and/or MAILPACE_ORGANIZATION_TOKEN set, build from source and point the client at build/index.js, or use the Dockerfile, which runs as a non-root user. MIT licensed.

Featured

Official AntV MCP server that turns a description of your data into a rendered chart — 26 visualization types from bar and line to sankey, mind-map, fishbone and geographic maps.

Payload's official MCP plugin — exposes every collection and global of a Payload CMS instance as MCP tools at /api/mcp, gated by Payload access control.

Trigger.dev's official MCP server — trigger and monitor background jobs, deploy to any environment, and query runs with TRQL from your coding agent.

MCP: Resend

by Resend

Featured

Resend's official MCP server for transactional and marketing email — send, schedule and batch messages, manage templates, contacts, broadcasts, automations, domains and suppressions from an agent.

Browse all MCP servers →