Quolle MCP
by Quolle-main
README.md
# Quolle MCP Server
Let AI agents — Claude Desktop, Cursor, and any [Model Context Protocol](https://modelcontextprotocol.io) client — send transactional email through [Quolle](https://quolle.com).
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. |
| `cancel_email` | Cancel a scheduled email before it sends. |
| `list_domains` | List your sending domains + verification status (to find a valid `from`). |
## Install & build
```bash
npm install
npm run build
```
## Configure your MCP client
You need a Quolle API key (starts with `qle_`) from your [dashboard](https://app.quolle.com) → API Keys.
### Claude Desktop
Add to `claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`):
```json
{
"mcpServers": {
"quolle": {
"command": "node",
"args": ["/absolute/path/to/quolle-mcp/dist/index.js"],
"env": {
"QUOLLE_API_KEY": "qle_your_api_key"
}
}
}
}
```
### Cursor
Add to `.cursor/mcp.json` in your project (or global settings):
```json
{
"mcpServers": {
"quolle": {
"command": "node",
"args": ["/absolute/path/to/quolle-mcp/dist/index.js"],
"env": { "QUOLLE_API_KEY": "qle_your_api_key" }
}
}
}
```
Once published to npm, you can skip the local build and use `npx`:
```json
{
"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 will call `list_domains` to confirm a valid sender, then `send_email`.
## 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
TDQS
A4.2/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: sending single or batch emails, retrieving status, canceling, and listing domains. No overlap exists.
Naming Consistency5/5
All tools follow a consistent verb_noun snake_case pattern: send_batch, get_email, cancel_email, list_domains, send_email.
Tool Count5/5
With 5 tools covering core email operations (send, batch send, status, cancel, domain management), the count is perfectly scoped for the domain.
Completeness5/5
The tool set covers essential lifecycle operations for transactional emails: sending, tracking, cancellation, and domain verification. No obvious gaps.
Maintenance
ActivitySlowing
ResponsivenessNo issues