Mail Send MCP server
{
"mcpServers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=mail-send"
}
}
}{
"mcpServers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=mail-send"
}
}
}{
"mcpServers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=mail-send"
}
}
}{
"servers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=mail-send"
}
}
}{
"mcpServers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=mail-send"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.12.0
What it does
MCP server for MailKite's transactional email service. It exposes tools to send emails over verified domains, manage templates and attachments, and handle inbound mail routing. Intended for AI agents and applications that need to send transactional email or give agents their own inbox.
- Send transactional emails from an AI agent using verified domains with custom headers and attachments.
- Route inbound emails to an agent's inbox for autonomous handling, filing, or escalation.
- Manage email domains and templates programmatically from within an AI workflow.
Tools this server exposes
| Tool | Does |
|---|---|
| send | Send a transactional email over a verified domain with optional templates, attachments, and custom headers. |
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.