Inbound Email MCP server
{
"mcpServers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
}
}
}{
"mcpServers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
}
}
}{
"mcpServers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
}
}
}{
"servers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
}
}
}{
"mcpServers": {
"mailkite": {
"type": "http",
"url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
}
}
}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
This server exposes MailKite's email API as MCP tools, allowing AI agents to send emails over verified domains, receive inbound messages as webhooks, and manage email-related configurations. It is for developers who want to give AI assistants email capabilities or route inbound mail to an agent for autonomous handling.
- Send emails from an AI agent using a verified domain through MailKite.
- Receive inbound emails as webhooks and parse them for processing or routing.
- Give an AI agent its own inbox where it can autonomously answer, file, or escalate messages.
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.