mcpbeat Sign in

Inbound Email MCP Server

answering

Inbound Email is answering right now. Last checked 1 min ago. Last commit 11 Sep 2026.

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

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
377 ms
Response time
average over 24h
0
Stars
last commit 11 Sep 2026

What the code does

We read the source, 22 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command prepack.mjs:18
execFileSync(process.execPath, [path.join(HERE, "gen-readme-tools.mjs")], { stdio: "inherit" });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add inbound-email --transport http https://mcp.mailkite.dev/mcp?ref=inbound-email
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "inbound-email": {
      "url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
    }
  }
}
~/.codex/config.toml
[mcp_servers.inbound-email]
url = "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
{
  "mcpServers": {
    "inbound-email": {
      "url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.mailkite.dev/mcp?ref=inbound-email streamable-http sign-in 508 ms 1 min ago

Alternatives to Inbound Email

same job, measured the same way
Mailkite
by mailkite

Send email, manage domains, DNS, webhooks, templates, and inbound routing on MailKite

128 installs/wk answering
Mail Receive
by mailkite

Receive inbound email as clean JSON — manage domains, routes, and webhooks. MailKite.

answering
Agent Mail
by mailkite

Give an AI agent its own inbox — receive email as a webhook, send over a verified domain.

answering
Temp Mail
by temp-mail

Disposable email inboxes for AI agents — read messages and verification codes.

answering
Email Agent
by mailkite

Email for AI agents — send, receive as a webhook, manage domains, templates, routing.

answering
Clawaimail
by joansongjr

Email infrastructure for AI agents. Create inboxes, send/receive email, and search messages.

42 installs/wk local only
MailFixture
by mailfixture

Test-inbox API for email and SMS: create inboxes, long-poll messages, extract OTPs and links.

answering
Shipmail MCP
by shipmail-to

Shipmail MCP server for AI agent custom-domain email inboxes with REST API and webhooks.

491 installs/wk answering

Inbound Email — questions

Answers built from our own checks of this server.

Why is there no tool list for Inbound Email?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Inbound Email working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 377 ms. The bar chart above shows every period we have measured.
How do I connect Inbound Email?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Inbound Email?
No API key is involved. Inbound Email answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Inbound Email?
It answers our handshake in 377 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Inbound Email open source?
We cannot say either way: written in JavaScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.