Mailtea vs Qmailing MCP Server
A side-by-side look at the Mailtea and Qmailing MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mailtea for communication work as a local process; choose Qmailing MCP Server for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mailtea when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
Choose Qmailing MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
QMAILING_API_TOKEN. - You want tools like
qmailing_list_mailboxes, qmailing_get_mailbox, qmailing_create_mailbox.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 45/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | QMAILING_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 10 |
| Full listing | View Mailtea | View Qmailing MCP Server |
Tools & capabilities
Mailtea tools
No tool names declared yet. Check the project README from the listing page.
Qmailing MCP Server tools 10
qmailing_list_mailboxesList every mailbox on the accountqmailing_get_mailboxFetch one mailbox by idqmailing_create_mailboxCreate a new mailbox under qmailing.com or a verified custom domainqmailing_list_domainsList custom domains and verification stateqmailing_get_dns_recordsDNS-records checklist for one domainqmailing_list_emailsList a mailbox folder (incl. `MUTED`); items carry `muted` + `suspicious` flagsqmailing_get_emailFetch one email with full body + attachment metadataqmailing_get_attachmentFetch one attachment's bytes (Base64, 5 MiB inline cap)qmailing_send_emailSend mail (recipients, subject, HTML/text, attachments)qmailing_register_webhookManage event webhooks
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Mailtea
{
"mcpServers": {
"mailtea": {
"command": "npx",
"args": [
"-y",
"plugins"
]
}
}
}
Qmailing MCP Server
{
"mcpServers": {
"thesameabramovych-qmailing-mcp-server": {
"command": "npx",
"args": [
"-y",
"@qmailing/mcp-server"
],
"env": {
"QMAILING_API_TOKEN": "YOUR_QMAILING_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Mailtea is categorized under Communication and uses a local stdio subprocess. Qmailing MCP Server belongs to Communication and uses a local stdio subprocess. Pick Mailtea for communication work and Qmailing MCP Server for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mailtea has no declared pricing — check the project's own site. Qmailing MCP Server is listed as a paid service. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mailtea and thesameabramovych-qmailing-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mailtea has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Qmailing MCP Server has 60/100 (Good) with 4 views, 0 installs and 1 GitHub stars.