Qmailing MCP Server

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:

{
  "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.