Community node
n8n
Send email and manage contacts, broadcasts, domains and suppressions inside your workflows. Or start a workflow when something happens to your email.
- Product
- Send and Mail
- Credential
- MepMail API: a full access Send key (ms_), since the trigger manages its own webhook. MepMail Correio API: a mailbox key (mmb_ or mmt_).
- Permissions
- In Mail the mailbox key decides: without send permission, the reply waits for the owner's approval.
- Send, schedule, cancel and batch send straight from a workflow node.
- The MepMail Trigger subscribes to the events you pick and registers (and removes) its own webhook automatically.
- Mail: start a workflow when email reaches an agent mailbox, read the message and save a reply draft.
- Payload signatures (Svix / Standard Webhooks) verified out of the box.
npm packageGitHub
Notification channels
Slack · Discord · Telegram
Point a webhook at your channel. MepMail uses the service's native format, without middleware or a relay service.
- Product
- Send events (deliveries, bounces, complaints, alerts)
- Credential
- None: paste the channel URL in Settings → Webhooks.
- 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.
Docs: notification channels
MCP server
AI agents
Claude, Cursor, VS Code and any Model Context Protocol client send email and manage the account through the MCP tools, on the same pipeline as the REST API.
- Product
- Send and account management; Mail mailboxes only with the mail permissions
- Endpoint
- https://api.mepmail.dev/mcp (hosted) or the @mepmail/mcp stdio package
- Credential
- OAuth when hosted; a Send key (ms_) for local stdio
- Permissions
- The ones you pick when connecting. Sending through the Send API goes out without approval, like any app's; sending from a mailbox asks for yours.
- Verified domains, suppressions, topic opt-outs, quotas and team scope all apply.
- With a Send key, the MCP creates mailboxes and agent keys without reading messages. Connected by OAuth with the mail permissions, it also reads and drafts in the mailboxes you tick.
Docs: MCP
Email inbox over MCP
Mail for agents
Give the agent its own mailbox on your domain. Through the Mail MCP it lists and reads messages, saves drafts and replies, no code.
- Product
- Mail
- Endpoint
- https://api.mepmail.dev/mcp/correio, or the Mail API at https://mepmail.dev/api/mailbox-agent
- Credential
- Mailbox key (mmb_ or mmt_), created in Mail → Agents
- Permissions
- Read, draft and send, per key. Without send, the draft waits for your approval.
- The agent lists and reads messages, saves drafts and replies in the conversation itself, without code.
- One key per mailbox (mmb_) or one for several of your mailboxes (mmt_). Revoke it any time in Mail.
- Each key's last use and last send show in Mail, and the mailbox history shows every agent action.
Explore MailDocs: connect an agent over MCP
Any app
SMTP relay
Ghost, Strapi, Supabase Auth and any app that sends over SMTP use the relay. On WordPress and WooCommerce, a common SMTP plugin bridges it.
- Product
- Send
- Endpoint
- smtp.mepmail.dev, port 2587
- Credential
- Username mepmail; password = a Send key (ms_), ideally sending only
- TLS required (STARTTLS).
- The same domains, suppressions, tracking and logs as the API.
Set it up in the dashboard
Migration
Resend SDKs: change only the baseUrl
Coming from Resend? Keep the official SDKs. Swap the base URL and the key, and your send calls stay the same.
- Product
- Send
- Endpoint
- https://api.mepmail.dev
- Credential
- Send key (ms_)
- 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.
Docs: SDKsMepMail vs Resend
Builders
CLI and REST API
Scripts, pipelines and internal tools call the same public API the dashboard uses, with 44 documented routes and an interactive reference.
- Product
- Send and account management
- Endpoint
- https://api.mepmail.dev
- Credential
- Send key (ms_): full access for management, or sending only
- @mepmail/cli runs the migration and day-to-day operations from the terminal.
- OpenAPI at docs.mepmail.dev. Send calls follow Resend's format; management is smaller than theirs (see the comparison).
Docs: CLIDocs: API reference