Quolle MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUOLLE_API_KEY | Yes | Your Quolle API key (starts with qle_). Required. | |
| QUOLLE_BASE_URL | No | Optional base URL for the Quolle API. Defaults to https://api.quolle.com. | https://api.quolle.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailA | Send one transactional email (OTP, receipt, notification, verification). Provide |
| send_batchA | 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. |
| get_emailA | Look up one email by id: status (queued, sent, delivered, bounced, complained, failed…) and open/click counts. |
| list_emailsA | List recent sends, newest first, optionally filtered by status or recipient. Needs a full-access API key. |
| cancel_emailA | Cancel a scheduled email that has not been sent yet. |
| list_domainsA | List the account's sending domains and whether each is verified. Use it to pick a valid |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.