Skip to main content
Glama
Quolle MCP

Quolle MCP

by Quolle-main

Quolle MCP Server

Let AI agents — Claude Desktop, Cursor, and any Model Context Protocol client — send transactional email through Quolle.

The agent gets tools to send email, send batches, check delivery status, cancel scheduled sends, and list your verified domains — so it can do things like "email the new signup their verification code" or "send everyone on this list their receipt" using your Quolle account.

Tools

Tool

What it does

send_email

Send one email (OTP, receipt, notification). Supports HTML or templates, scheduling, and idempotency.

send_batch

Send up to 100 emails in one all-or-nothing request.

get_email

Check an email's delivery status and open/click counts by ID.

list_emails

List recent sends, filtered by status or recipient.

cancel_email

Cancel a scheduled email before it sends.

list_domains

List your sending domains + verification status (to find a valid from).

Every tool carries MCP annotations (readOnlyHint, destructiveHint), so clients can auto-approve the read-only ones and ask before a send or cancel.

Transactional only. There's deliberately no way to send marketing mail from an agent; use Campaigns for that, where consent and unsubscribes are enforced.

Use a sending-only key (Dashboard → API Keys → scope "Sending"). It can send, look up and cancel emails, which is all an agent usually needs. list_domains and list_emails need a full-access key. You can also restrict a key to specific sending domains.

Errors keep the API's code (for example domain_not_verified, rate_limit_exceeded), so the agent can tell "fix the request" from "wait and retry". Rate-limited calls are retried automatically.

Related MCP server: GetMailer MCP Server

Install

Once published, no install step is needed; point your client at npx -y @quolle/mcp (below). To run from source instead:

npm install
npm run build
# then use "command": "node", "args": ["/absolute/path/to/quolle-mcp/dist/index.js"]

Configure your MCP client

You need a Quolle API key (starts with qle_) from your dashboard → API Keys.

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "quolle": {
      "command": "npx",
      "args": ["-y", "@quolle/mcp"],
      "env": {
        "QUOLLE_API_KEY": "qle_your_sending_key"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project (or global settings):

{
  "mcpServers": {
    "quolle": {
      "command": "npx",
      "args": ["-y", "@quolle/mcp"],
      "env": { "QUOLLE_API_KEY": "qle_your_sending_key" }
    }
  }
}

Once published to npm, you can skip the local build and use npx:

{
  "mcpServers": {
    "quolle": {
      "command": "npx",
      "args": ["-y", "@quolle/mcp"],
      "env": { "QUOLLE_API_KEY": "qle_your_api_key" }
    }
  }
}

Try it

After restarting your MCP client, ask the agent:

"Using Quolle, send a test email from hello@mail.mydomain.com to me@example.com with the subject 'Hello from my agent' and a short HTML body."

The agent calls send_email (and, with a full-access key, may first call list_domains to confirm a verified sender).

Environment

  • QUOLLE_API_KEY — required. Your Quolle API key.

  • QUOLLE_BASE_URL — optional, defaults to https://api.quolle.com.

Safety

Sends go through your real Quolle account and count against your quota. To test agent flows without touching your reputation, point the agent at Quolle's reserved test addresses: delivered@test.quolle.com, bounced@test.quolle.com, complained@test.quolle.com.

License

MIT

Available Tools

6 tools
cancel_emailCancel a scheduled emailA
DestructiveIdempotent

Cancel a scheduled email that has not been sent yet.

Inputs: id (required).

get_emailGet email statusA
Read-only

Look up one email by id: status (queued, sent, delivered, bounced, complained, failed…) and open/click counts.

Inputs: id (required).

list_domainsList sending domainsA
Read-only

List the account's sending domains and whether each is verified. Use it to pick a valid from before sending. Needs a full-access API key.

Inputs: no named parameters.

list_emailsList recent emailsA
Read-only

List recent sends, newest first, optionally filtered by status or recipient. Needs a full-access API key.

Inputs: limit, status, recipient.

send_batchSend a batch of emailsA

Send up to 100 emails in one all-or-nothing request (no attachments in a batch). Each item takes the same fields as send_email.

Inputs: emails (required), idempotencyKey.

send_emailSend emailA

Send one transactional email (OTP, receipt, notification, verification). Provide html with subject, or a template slug with variables. The from domain must be verified. Pass an idempotencyKey (e.g. the order or user id plus purpose) so that if you retry, the email is not sent twice.

Inputs: to (required), from (required), html, text, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action: sending (single vs. batch is clearly delimited by the 100-email, all-or-nothing description), lookup by id vs. listing, cancellation, and domain listing. No two tools could plausibly be chosen for the same intent.

    Naming Consistency5/5

    All six tools follow a strict verb_noun snake_case pattern (send_email, send_batch, get_email, list_emails, list_domains, cancel_email). Verb choices are standard CRUD-style and predictable.

    Tool Count5/5

    Six tools is well within the ideal 3-15 range and each earns its place in a transactional email workflow (send, batch send, cancel, inspect, list, validate sender domain). Nothing looks like padding or a leftover utility.

    Completeness3/5

    Core send/read/cancel flow is covered, but cancel_email implies scheduled sends exist while no tool lets an agent schedule one, and domain verification/creation and template discovery or management are absent even though send_email accepts template slugs. These are meaningful gaps an agent would hit in real workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to send transactional emails programmatically through the Lemon Email API. Provides simple email sending capabilities with customizable sender information, recipients, and content.
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables sending transactional emails through GetMailer from AI assistants. Supports email operations, template management, domain verification, analytics, suppression lists, and batch email jobs.
      14
      18 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send transactional email, authenticate sending domains, track delivery, and diagnose deliverability issues programmatically.
      13
      87 npm
      MIT