Turn inbound email into a webhook — verify, parse, route, and store incoming messages.
Install
Run one of the commands below, then add the client config underneath.
https://mcp.mailkite.dev/mcp?ref=inbound-emailClient configuration
Paste into Claude Desktop, Cursor (mcp.json), VS Code or any MCP client, then restart the client.
{
"mcpServers": {
"inbound-email": {
"url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
}
}
}About this server
Inbound Email is listed in the Communication category of the MCPNav directory. It is distributed as Streamable HTTP and can be loaded by any client that speaks the Model Context Protocol.
Typical uses include giving your assistant scoped access to the corresponding service so it can answer questions and take actions with real data instead of guessing. Always review what a server can access before you enable it — see our MCP security guide.
Frequently asked questions
What is the Inbound Email MCP server?＋
Inbound Email is an MCP server by mailkite. Turn inbound email into a webhook — verify, parse, route, and store incoming messages.
How do I install Inbound Email?＋
Install it with: https://mcp.mailkite.dev/mcp?ref=inbound-email. Then add the JSON config to your client's MCP settings and restart the client.
Is Inbound Email free to use?＋
The MCP server itself is free to install. The source is public on https://github.com/mailkite/mailkite-mcp. Any third-party API it calls (such as a search or maps API) may require its own key and billing.
Which clients support Inbound Email?＋
Any MCP-compatible client can use it, including Claude Desktop, Cursor, VS Code, Windsurf and custom agents.