mcpbeat Sign in

Email Inbox API + Sending by Sendmux MCP Server

answering

Email Inbox API + Sending by Sendmux is answering right now. Last checked 1 min ago. 135 installs a week from pypi. Last commit 18 Sep 2026.

AI email inbox and sending tools with attachments, search, live events, and webhooks.

Installs per day peak 401 · avg 69 · -66% w/w
a month agotoday
Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
195 ms
Response time
average over 24h
135
Installs / week
npm and PyPI

What the code does

We read the source, 20 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.

File ships in the package but is absent from the source [пакет] sendmux_mcp/__init__.py:1, [пакет] sendmux_mcp/__main__.py:1, [пакет] sendmux_mcp/cli.py:1 и ещё 17
этот файл ставится пользователю, но в репозитории его нет
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Builds a database query by concatenation .github/workflows/release-please.yml:183
      - name: Update Homebrew tap
        if: ${{ contains(needs.release-please.outputs.paths_released, 'packages/ts/cli') }}

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 sendmux-mcp --transport http https://mcp.sendmux.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sendmux-mcp": {
      "url": "https://mcp.sendmux.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.sendmux-mcp]
url = "https://mcp.sendmux.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sendmux-mcp": {
      "url": "https://mcp.sendmux.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "sendmux-mcp": {
      "url": "https://mcp.sendmux.ai/mcp"
    }
  }
}

This one needs environment variables set before it will start: SENDMUX_MCP_SURFACES (Tool surfaces to run locally.), SENDMUX_MAILBOX_API_KEY (Mailbox API key for Mailbox API and Sending API tools.), SENDMUX_MANAGEMENT_API_KEY (Root API key for Management API tools.), SENDMUX_SENDING_API_KEY (Optional send-capable smx_mbx_ key or owner-approved smx_agent_ token for Sending API tools when it differs from the Mailbox API key.). The author declared them in the registry entry; get the values from the project itself.

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.sendmux.ai/mcp streamable-http sign-in 441 ms 1 min ago

Alternatives to Email Inbox API + Sending by Sendmux

same job, measured the same way
Sentvia
by sentvia

Email for AI agents: inboxes, send/reply/forward, search, threads, webhooks — 21 SentVia tools.

56 installs/wk local only
Sentfrom
by sentfrom

Email for AI agents: inboxes, send/reply/forward, search, threads, webhooks — 21 SentFromAI tools.

39 installs/wk local only
Commune
by shanjai-raj

Email and SMS MCP server for AI agents — 41 tools for inboxes, sending, search, and SMS.

147 installs/wk local only
MCP Email
by infoinlet-marketplace

Email for AI agents — read inbox (IMAP), search, and send (SMTP).

32 installs/wk local only
Qmailing
by qmailing

AI agents read & send email, manage mailboxes, domains and webhooks via the QMailing API.

67 installs/wk 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
Engagelab Email
by r1ghtherewaiting

Send, receive, monitor and reply to email from AI agents with threaded inbox context.

35 installs/wk local only
Agent Cold Email
by ys-projectcalc

Coldrig — cold-email infra run by your agent: 28 MCP tools, live sending, free sandbox. $99/mo.

33 installs/wk 28 tools answering

Email Inbox API + Sending by Sendmux — questions

Answers built from our own checks of this server.

Why is there no tool list for Email Inbox API + Sending by Sendmux?
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 Email Inbox API + Sending by Sendmux 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 195 ms. The bar chart above shows every period we have measured.
How do I connect Email Inbox API + Sending by Sendmux?
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 Email Inbox API + Sending by Sendmux?
No API key is involved. Email Inbox API + Sending by Sendmux 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 Email Inbox API + Sending by Sendmux?
It answers our handshake in 195 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Email Inbox API + Sending by Sendmux?
The pypi package sendmux-mcp was installed 135 times in the last week. Week over week that is -66%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Email Inbox API + Sending by Sendmux open source?
Yes — it is published under the MIT licence, written in PHP and 73 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.