# TheSameAbramovych/qmailing-mcp-server [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/TheSameAbramovych/qmailing-mcp-server  
**GitHub Stars:** 1  
**npm Downloads (last month):** 342  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/thesameabramovych-qmailing-mcp-server

## Description
AI agents read & send email, manage mailboxes, custom domains and webhooks via the QMailing API (npm stdio + hosted OAuth connector).

## Tools
Capabilities this server exposes over MCP:

- **qmailing_list_mailboxes** — List every mailbox on the account
- **qmailing_get_mailbox** — Fetch one mailbox by id
- **qmailing_create_mailbox** — Create a new mailbox under qmailing.com or a verified custom domain
- **qmailing_list_domains** — List custom domains and verification state
- **qmailing_get_dns_records** — DNS-records checklist for one domain
- **qmailing_list_emails** — List a mailbox folder (incl. `MUTED`); items carry `muted` + `suspicious` flags
- **qmailing_get_email** — Fetch one email with full body + attachment metadata
- **qmailing_get_attachment** — Fetch one attachment's bytes (Base64, 5 MiB inline cap)
- **qmailing_send_email** — Send mail (recipients, subject, HTML/text, attachments)
- **qmailing_register_webhook** — Manage event webhooks

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "qmailing-mcp-server": {
    "command": "npx",
    "args": ["-y","@qmailing/mcp-server"],
    "env": {
      "QMAILING_API_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `QMAILING_API_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What TheSameAbramovych/qmailing-mcp-server MCP server does

TheSameAbramovych/qmailing-mcp-server MCP server connects an MCP-compatible agent to the QMailing API. It provides read and write operations for mailboxes, email, custom domains, attachments, and event webhooks. Agents can inspect account mailboxes, create mailboxes on QMailing domains or verified custom domains, and check domain verification details and DNS records.

Email tools cover folder listings, individual message retrieval, attachment downloads, and sending messages. Listed email objects include `muted` and `suspicious` indicators, and attachment retrieval returns Base64 data with a 5 MiB inline limit. Webhook tools support registering, listing, and deleting event webhooks.

## How it works

TheSameAbramovych/qmailing-mcp-server MCP server offers two connection patterns. Local MCP clients launch the npm package as a stdio process. The process reads `QMAILING_API_TOKEN` and uses it as a bearer credential for QMailing API requests. `QMAILING_API_URL` can override the default API host for staging or self-hosted deployments.

Claude.ai uses a different path: connect the hosted endpoint at `https://qmailing.com/mcp` as a custom connector. Authentication occurs through OAuth in the browser, with scope consent during connection and refresh-token rotation handled by the service. Both paths expose the same general tool surface, but they differ in authentication and transport.

Email content should be treated as untrusted data rather than agent instructions. The server marks read results with a security note and an untrusted-content metadata value. Workflows should pay attention to suspicious messages, avoid acting on requests found in email without confirmation, and grant only the scopes they need.

## Setup and configuration

For the local package, use Node.js 18.17 or later and a QMailing account on the PLUS tier or higher. Generate an API token from QMailing Settings → Developers, select the required scopes, and provide it to the MCP client's environment. A direct configuration uses:

```json
{
  "command": "npx",
  "args": ["-y", "@qmailing/mcp-server"],
  "env": {
    "QMAILING_API_TOKEN": "qm_live_..."
  }
}
```

The token is shown only when created and should be handled like a password. It can be revoked from the QMailing developer settings. The default API URL is `https://qmailing.com`; set `QMAILING_API_URL` only when targeting another supported deployment.

## Tools and capabilities

TheSameAbramovych/qmailing-mcp-server MCP server includes tools for:

- Listing and fetching mailboxes, plus creating new mailboxes.
- Listing custom domains and retrieving DNS verification records.
- Listing messages by folder, including `MUTED`, and fetching full message content.
- Downloading attachment bytes as Base64.
- Sending text or HTML email with recipients and attachments.
- Registering, listing, and deleting event webhooks.

Access is divided by scopes such as `mailboxes:read`, `mailboxes:write`, `domains:read`, `email:read`, `email:send`, and `webhooks:manage`.

## Limitations and notes

The token-based API is gated on the PLUS plan or higher. Existing tokens are disabled if the account is downgraded. Email subjects, bodies, sender names, and attachment filenames may contain prompt-injection content, so sending mail or changing webhooks should remain subject to explicit user approval. The local process keeps the token in the launched environment and sends it to the QMailing API for authentication.

The project is licensed under MIT. Its local package requires a compatible MCP client with stdio support; Claude.ai uses the separate hosted OAuth connector instead.

_Full upstream README: https://allmcps.com/mcp/thesameabramovych-qmailing-mcp-server/readme_