Skip to content

Integrations

Your stack stays. Delivery upgrades.

Connect your workflows, team chat, AI agents and existing apps to MepMail. They all use the same sending pipeline, with verified domains, suppressions, quotas and logs.

One API key and one verified domain cover everything on this page.

Works with your stack

  • n8n
  • Slack
  • Discord
  • Telegram
  • Node.js
  • Python
  • PHP
  • Ruby
  • Go
  • Docker
  • cURL

Community node

n8n

  • n8n

Send email and manage contacts, broadcasts, domains and suppressions inside your workflows. Or start a workflow when something happens to your email.

  • Send, schedule, cancel and batch messages from a workflow node.
  • MepMail Trigger subscribes to the events you pick and registers (and removes) its own webhook automatically.
  • Payload signatures (Svix / Standard Webhooks) verified out of the box.
  • Works with MepMail Cloud or any self-hosted instance. Requires a full access API key.

Notification channels

Slack · Discord · Telegram

  • Slack
  • Discord
  • Telegram

Point a webhook at your channel. MepMail uses the service's native format, without middleware or a relay service.

  • Paste the incoming-webhook URL: Slack, Discord and Telegram are detected and formatted natively (Telegram takes the sendMessage URL with your chat id).
  • Deliveries, bounces, complaints and deliverability alerts land where the team already is.
  • Every other endpoint keeps the raw signed JSON. The same webhooks, with nothing extra to configure.

MCP server

AI agents

  • MCP

Claude Code, Cursor, VS Code and any Model Context Protocol client send email and manage the platform through 22 tools, on the same pipeline as the REST API.

  • Streamable HTTP endpoint at /mcp on your API origin, or the stdio server on npm.
  • Verified domains, suppressions, topic opt-outs, quotas and team scoping all apply unchanged.

Any app

SMTP relay

WordPress, WooCommerce, Ghost, Strapi, Supabase or any other application that sends over SMTP can use the relay with your key.

  • Host, port and credentials; TLS required.
  • Same domains, suppressions, tracking and logs as the API.
  • No plugin to install and nothing to patch.

Migration

Resend SDKs, drop-in

  • Node.js
  • Python
  • PHP
  • Ruby
  • Go

Coming from Resend? Keep the official SDKs. Change the base URL and the key, and your send calls stay exactly as they are.

  • Nine languages documented, with the base-URL rules of each SDK (trailing slash included).
  • The free account moves with one command: npx @mepmail/cli migrate --from resend.

Builders

CLI and REST API

  • cURL

Scripts, pipelines and back-office tools call the same public API the panel uses: 44 documented endpoints with an interactive reference.

  • @mepmail/cli runs the migration and day-to-day operations from the terminal.
  • OpenAPI at docs-mepmail.je4ndev.com, wire-compatible with the Resend API surface.

Ship with the stack you already run.

Create the free account, connect the first integration and send a real email today.

Create free account