
Mailersend
Let your agent send transactional mail, configure MailerSend domains, and inspect delivery analytics while you wire email into a SaaS backend.
Overview
MailerSend is an MCP server for the Build phase that sends transactional email, manages domains, and surfaces delivery analytics via MailerSend’s API.
What is this MCP server?
- Send transactional emails through MailerSend from agent-driven workflows
- Manage sending domains and related MailerSend account operations
- Access delivery analytics for debugging sends and engagement
- Stdio MCP via mcparmory-mailersend (uvx) or Docker OCI at version 1.0.2
- Communication-focused MCP—not a template design or copywriting skill
- Server version 1.0.2
- 2 packages: PyPI uvx and OCI Docker
- Stdio MCP transport
Community signal: 25 GitHub stars.
What problem does it solve?
Hooking up password resets, receipts, and alerts means repetitive dashboard clicks and API docs paste cycles your agent cannot do without a MailerSend MCP bridge.
Who is it for?
Solo builders shipping a SaaS who already use MailerSend and want the coding agent to operate sends and domains during backend work.
Skip if: Builders who only need local email capture in dev, bulk marketing automation without MCP, or providers you do not use on MailerSend.
What do I get? / Deliverables
Once registered, your agent can trigger sends, adjust domains, and pull delivery metrics so email integration ships faster with fewer manual API calls.
- Agent-callable MailerSend send and domain tools
- Faster wiring of transactional flows in your codebase
- Queryable delivery analytics from within the agent session
Recommended MCP Servers
Journey fit
Email provider hooks belong in Build when you connect production services rather than during pure ideation. Integrations is the subphase for third-party APIs like MailerSend that power signup, reset-password, and billing emails.
How it compares
MailerSend API MCP integration, not an email copywriting or journey-wide methodology skill.
Common Questions / FAQ
Who is com.mcparmory/mailersend for?
Developers on MailerSend who use MCP agents to implement and operate transactional email during product build and early growth.
When should I use com.mcparmory/mailersend?
Use it while integrating or debugging transactional email, domain setup, and delivery stats in your app with an AI coding assistant.
How do I add com.mcparmory/mailersend to my agent?
Configure the stdio MCP server with mcparmory-mailersend via uvx or the ghcr.io/mcparmory/mailersend image, set MailerSend API credentials in the server environment, and reload your client.