Quolle MCP
The server exposes Quolle MCP tools for sending and managing transactional email.
send_email: send one transactional email via HTML or a saved template, with optional text, reply-to, template variables, future scheduling, and idempotency; recipients can be one address or up to 50.send_batch: send 1–100 emails in one all-or-nothing request.get_email: look up a single email by ID for delivery status and open/click counts.cancel_email: cancel a scheduled email that has not sent yet.list_domains: list sending domains and verification status to find a validfromaddress.Intended for transactional mail such as OTPs, receipts, notifications, and verifications; the schema does not include the README’s
list_emailstool.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Quolle MCP Send a test email to me@example.com from hello@myverifieddomain.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 one email (OTP, receipt, notification). Supports HTML or templates, scheduling, and idempotency. |
| Send up to 100 emails in one all-or-nothing request. |
| Check an email's delivery status and open/click counts by ID. |
| List recent sends, filtered by status or recipient. |
| Cancel a scheduled email before it sends. |
| List your sending domains + verification status (to find a valid |
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 tohttps://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 toolscancel_emailCancel a scheduled emailADestructiveIdempotent
Cancel a scheduled email that has not been sent yet.
Inputs: id (required).
get_emailGet email statusARead-only
Look up one email by id: status (queued, sent, delivered, bounced, complained, failed…) and open/click counts.
Inputs: id (required).
list_domainsList sending domainsARead-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 emailsARead-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
Scored across 6 tools
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.
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.
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.
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
Related MCP Connectors
Send email, manage domains, templates, webhooks and broadcasts from your AI agent.
Transactional email for AI agents: templates, domain verify, and sends.
Send transactional emails for AI agents via SMTP. Templates included.
Send transactional email and manage domains, templates and webhooks in UniOne from AI agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to send transactional emails programmatically through the Lemon Email API. Provides simple email sending capabilities with customizable sender information, recipients, and content.2MIT
- AlicenseAqualityDmaintenanceEnables sending transactional emails through GetMailer from AI assistants. Supports email operations, template management, domain verification, analytics, suppression lists, and batch email jobs.1418 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to manage email mailboxes, send and receive emails, and handle webhooks via qmailing.1262 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to send transactional email, authenticate sending domains, track delivery, and diagnose deliverability issues programmatically.1387 npmMIT