Inbound Email

dev.mailkite/inbound-email · v0.12.0

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

Website Source code Set it up

Connect Remote server

Terminal

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

~/.cursor/mcp.json

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

.vscode/mcp.json

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

Claude Desktop

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

Tools

This server asks for a key before it lists its tools. Connect it with your own key to see them.

Details

Endpoint	`https://mcp.mailkite.dev/mcp?ref=inbound-email` (Streamable HTTP)
First published	4 Jul 2026
Last updated	4 Jul 2026
Registry name	`dev.mailkite/inbound-email`

More communication servers See all

Live status

Live, key required

Typical response: 883 ms
Answered: 100% of 2 checks
Last check: 13 Nov 2026

30 days agoToday

We connect daily without credentials and run initialize and tools/list.

Pair it with live search

Agents that use Inbound Email often also need current facts. NestDaddy MCP gives your AI today's internet: web search, real-time breaking news and full page reading in one connector.

See NestDaddy MCP

For maintainers

[![NestDaddy MCP](https://nestdaddy.com/mcp/servers/dev-mailkite-inbound-email/badge.svg)](https://nestdaddy.com/mcp/servers/dev-mailkite-inbound-email)

Add the badge to your README. It turns green while your server passes our daily check. Listing details come from the official MCP registry; update them there.

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.