Email Send API
Wire your coding agent to send transactional or product emails through Resend as a remote MCP tool instead of hand-rolling SMTP or REST glue.
Overview
io.github.Br0ski777/email-send is a MCP server for the Build phase that sends text or HTML email through Resend via a remote SSE endpoint with x402 micropayment.
What is this MCP server?
- Sends email via Resend with plain text and HTML body support
- Hosted remote MCP over SSE at email-send.api.klymax402.com
- x402 micropayment gate on API calls (pay-per-use, no flat SaaS-only assumption)
- Server manifest version 1.1.0 with MCP server schema 2025-12-11
- Open-source reference repo: github.com/Br0ski777/email-send-x402
- 1 remote SSE endpoint: email-send.api.klymax402.com/mcp
- Supports text and HTML email formats per server description
What problem does it solve?
Agents can write email copy but cannot reliably send it without you building and maintaining a separate Resend or SMTP integration.
Who is it for?
Indie builders adding password-reset, notification, or waitlist emails to a new SaaS or API while coding with an MCP-enabled agent.
Skip if: Teams that need bulk marketing, deep analytics, or compliance-heavy enterprise deliverability without handling Resend accounts themselves.
What do I get? / Deliverables
After you add the remote MCP URL, your agent can call a send tool and deliver Resend-backed messages from the same workflow where you ship features.
- Agent-invoked email send with text or HTML content
- MCP tool surface documented in server.schema.json 2025-12-11 manifest
Recommended MCP Servers
Journey fit
Outbound email is a product integration solo builders add while wiring backends, auth flows, and notifications during the build phase. Fits the integrations subphase because it connects the agent stack to a third-party email provider (Resend) over MCP.
How it compares
Remote MCP email bridge with x402 metering, not a standalone agent skill or full ESP dashboard.
Common Questions / FAQ
Who is io.github.Br0ski777/email-send for?
Solo and indie builders who want Claude Code, Cursor, or Codex to send Resend-backed transactional email through MCP during product development.
When should I use io.github.Br0ski777/email-send?
Use it in the build phase when you are wiring auth, billing, or notification flows and need the agent to trigger real sends instead of only drafting templates.
How do I add io.github.Br0ski777/email-send to my agent?
Register the remote SSE MCP server URL https://email-send.api.klymax402.com/mcp in your client’s MCP config, complete x402 USDC payment setup per the repo, and ensure Resend is configured for your sending domain.