mailkite
Send email, manage domains, DNS, webhooks, templates, and inbound routing on MailKite
Open the source (opens github.com) https://github.com/mailkite/mailkite-mcp
Before you use it
- Runs on someone else's server: what you send it leaves your machine.
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: MAILKITE_API_KEY. Use a key with the least access you can.
What it is
MCP servers from dev.mailkite.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
@mailkite/mcp@0.13.0
From the server's entry in the official MCP Registry
Remote endpoint (streamable-http)
https://mcp.mailkite.dev/mcp
From the server's entry in the official MCP Registry
Settings it asks for
MAILKITE_API_KEYsecret required · MailKite API key (mk_live_…) from the dashboard at https://app.mailkite.dev
Related
-
mail-receive
MCP serversReceive inbound email as clean JSON — manage domains, routes, and webhooks. MailKite.
-
mail-send
MCP serversSend transactional email over a verified domain — templates, attachments, custom headers.
-
email-agent
MCP serversEmail for AI agents — send, receive as a webhook, manage domains, templates, routing.
-
inbound-email
MCP serversTurn inbound email into a webhook — verify, parse, route, and store incoming messages.
-
agent-mail
MCP serversGive an AI agent its own inbox — receive email as a webhook, send over a verified domain.
-
GitHub MCP server
MCP serversGitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.
https://api.githubcopilot.com/mcp/