Send emails programmatically via Resend. Text and HTML. x402 micropayment.
Email Send API MCP server exists for a simple reason — assistants are far more useful when they can act on Email Send API directly instead of describing what you should do. Send emails programmatically via Resend. Text and HTML. x402 micropayment.
Send emails programmatically via Resend -- text or HTML body, delivery status, message ID. Transactional email. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Once Email Send API is connected, these are the calls the assistant has available:
email_send_message — POSTSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Email Send API's toolset — email_send_message — is a fair guide to whether it matches your workflow. It is maintained by Br0ski777; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| email_send_message | POST |
{
"mcpServers": {
"email-send": {
"url": "https://email-send.api.klymax402.com/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.