CamelMailer MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAMELMAILER_API_KEY | Yes | Server API key from your CamelMailer dashboard. | |
| CAMELMAILER_BASE_URL | No | Base URL of your CamelMailer instance. Defaults to https://app.camelmailer.com | https://app.camelmailer.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 a transactional email through CamelMailer. Provide html_body and/or text_body. Queues one message per recipient and returns their ids. |
| send_email_with_templateA | Render a stored CamelMailer template (Mustache-style {{ variables }}) against template_model and send it. Fields set directly (e.g. subject) override the rendered ones. |
| list_emailsA | List messages of the CamelMailer server, newest first. Filter by scope, status, tag, substring query or message stream. |
| get_emailA | Retrieve one message by id, including its SMTP delivery attempts. |
| list_templatesB | List all stored message templates of the CamelMailer server. |
| render_templateA | Preview a stored template rendered against a variable model — returns the rendered subject, html_body and text_body without sending anything. |
| get_statsB | Message counters of the server (sent, pending, bounced, opens, clicks, …), optionally limited to a created_at time window. |
| list_bouncesC | List bounced messages, filtered and paginated. |
| dmarc_summaryB | DMARC compliance summary over the stored aggregate reports: pass rate, top sending sources and disposition totals. |
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 9 tools
Each tool targets a distinct operation: raw send, template send, list, get, template list, preview, stats, bounces, and DMARC summary. There is no overlap or ambiguity among them.
Most tools follow a verb_noun pattern (send_email, list_emails, get_email, render_template). The exception is dmarc_summary, which lacks a verb, but the pattern is otherwise consistent and readable.
With 9 tools, the set is well-scoped for a transactional email server covering sending, retrieval, templating, stats, and DMARC. Each tool earns its place without being overwhelming or sparse.
Core email lifecycle (send, list, get, bounce) and monitoring (stats, DMARC) are covered. The main gap is lack of template create/update/delete, but since templates can be managed externally, this is a minor workaround.