mcpbeat Sign in

Qmailing MCP Server

by qmailing Your server? Claim it
answering

Qmailing is answering right now. Last checked 4 min ago. 40 installs a week from npm. Last commit 14 Jun 2026.

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

Installs per day peak 24 · avg 10 · +48% w/w
a month agotoday
Uptime history 51 days of history · worst day 97%
51 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
225 ms
Response time
average over 24h
40
Installs / week
npm and PyPI

Nothing serious here today

Today is the operative word: we check Qmailing every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 4 min ago.

run in your terminal
claude mcp add mcp-server --transport http https://qmailing.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://qmailing.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://qmailing.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://qmailing.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://qmailing.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: QMAILING_API_TOKEN (API token from https://qmailing.com/settings/developers). 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://qmailing.com/mcp streamable-http sign-in 197 ms 4 min ago

Alternatives to Qmailing

same job, measured the same way
MailMask
by mailmask

Email for agents: domains, aliases, IMAP mailboxes, DNS, sending and webhooks via one API key.

answering
Email Agent
by mailkite

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

answering
RacterMX
by racter-ciso

Manage RacterMX email forwarding — domains, aliases, webhooks, and more — via AI.

34 installs/wk local only
Mailkite
by mailkite

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

76 installs/wk answering
Sendhustle MCP
by achlesha

Send and manage email via the SendHustle API — emails, domains, contacts, audiences, campaigns.

70 installs/wk local only
Shipmail MCP
by shipmail-to

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

277 installs/wk answering
Sentvia
by sentvia

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

32 installs/wk local only
Sentfrom
by sentfrom

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

31 installs/wk local only

Qmailing — questions

Answers built from our own checks of this server.

Why is there no tool list for Qmailing?
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 Qmailing working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 225 ms. The bar chart above shows every period we have measured.
How do I connect Qmailing?
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 Qmailing?
No API key is involved. Qmailing 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 Qmailing?
It answers our handshake in 225 ms on average, which is faster than 64% 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 Qmailing?
The npm package @qmailing/mcp-server was installed 40 times in the last week. Week over week that is +48%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Qmailing open source?
Yes — it is published under the MIT licence, written in TypeScript and 1 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.