Turn inbound email into a webhook — verify, parse, route, and store incoming messages.
dev.mailkite/inbound-email MCP Server
This MCP server turns inbound email into a webhook. It verifies incoming messages, parses their contents, routes them, and stores the resulting data for downstream use. It is positioned as the official MailKite library for AI agents (MCP), focused on email delivery into agent workflows.
🛠️ Key Features
Inbound email received as a webhook
Verification of incoming messages
Parsing of email content
Routing and storing of incoming messages
🚀 Use Cases
Provide an AI agent with an inbox for incoming email
Enable email-to-webhook integration for product workflows
⚡ Developer Benefits
Uses the official MailKite library for AI agents (MCP)
Standardizes how inbound email is transformed into agent-consumable messages
⚠️ Limitations
Limited details available in the provided source on supported providers, storage format, and routing rules beyond “route and store.”
Email for every product you ship — receive email as a webhook, send over a verified domain, give an AI agent its own inbox.
The official MailKite library for AI agents (MCP).
Read-only mirror. This repo is a generated, release-time mirror of the MailKite monorepo (the private source of truth) — development doesn't happen here. Install from npm and open issues against the MailKite docs.
MailKite speaks the Model Context Protocol: every API method is a tool your AI assistant (Claude, Cursor, …) can call — send mail, manage domains, search the docs, and give an agent its own inbox. Full guide: https://mailkite.dev/docs/ai-agents.
Hosted (recommended) — one-click OAuth, no key to copy:
bash
claude mcp add --transport http mailkite https://mcp.mailkite.dev/mcp
Give an agent its own inbox. Route inbound mail to a built-in inbox agent (the agent route action) and it answers, files, or escalates on its own — see https://mailkite.dev/docs/ai-agents.
