inbound-email

dev.mailkite/inbound-emailVersion 0.12.0

Turn inbound email into a webhook — verify, parse, route, and store incoming messages.

Status

Sign-in required609 msNov 14, 2026, 14:30 UTCReachable. It asks for authorization, so we did not look inside.

We could not refresh it, so this page shows the last copy.

Data from the official MCP Registry, checked by run.zero. How we check

Streamable HTTP

https://mcp.mailkite.dev/mcp?ref=inbound-emailSign-in required609 msNov 14, 2026, 14:30 UTC

OAuth sign-in

This server asks for sign-in. Your client opens the sign-in when it connects.

claude mcp add --transport http inbound-email 'https://mcp.mailkite.dev/mcp?ref=inbound-email'

1
2
3

Settings > Connectors > Add custom connector
Name: inbound-email
Remote MCP server URL: https://mcp.mailkite.dev/mcp?ref=inbound-email

{
  "mcpServers": {
    "inbound-email": {
      "url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
    }
  }
}

code --add-mcp '{"name":"inbound-email","type":"http","url":"https://mcp.mailkite.dev/mcp?ref=inbound-email"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Tools are visible after sign-in; we do not look inside protected servers.

Registry status: Active
Published: Jul 4, 2026
Updated: Jul 4, 2026
Website: https://mailkite.dev/docs/ai-agents⁠ (opens in a new tab)
Repository: https://github.com/mailkite/mailkite-mcp⁠ (opens in a new tab)
Categories (suggested): CommunicationSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared