Skip to main content
Glama
CamelMailer MCP Server

CamelMailer MCP Server

Official
by camelmailer

Camelmailer MCP Server

CI npm License: MIT

Model Context Protocol server for Camelmailer — lets AI assistants like Claude send and inspect transactional email. Works with the Camelmailer cloud and any self-hosted instance.

Setup

You need a server API key from your Camelmailer dashboard.

Claude Desktop

Add to claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "camelmailer": {
      "command": "npx",
      "args": ["-y", "@camelmailer/mcp"],
      "env": {
        "CAMELMAILER_API_KEY": "cm_xxxx"
      }
    }
  }
}

Claude Code

claude mcp add camelmailer -e CAMELMAILER_API_KEY=cm_xxxx -- npx -y @camelmailer/mcp

Self-hosted instances

Point the server at your own instance (defaults to https://app.camelmailer.com):

"env": {
  "CAMELMAILER_API_KEY": "cm_xxxx",
  "CAMELMAILER_BASE_URL": "https://mail.example.com"
}

Related MCP server: Tratto MCP Server

Tools

Tool

Description

send_email

Send an email with html_body / text_body

send_email_with_template

Render a stored template against variables and send

list_emails

List messages (filter by scope, status, tag, query, stream)

get_email

One message incl. SMTP delivery attempts

list_templates

All stored message templates

render_template

Preview a rendered template — no send

get_stats

Message counters (sent, bounced, opens, clicks, …)

list_bounces

Bounced messages

dmarc_summary

DMARC pass rate and top sending sources

list_streams get_stream create_stream update_stream archive_stream

Message streams

send_to_stream

Sends now to every subscriber of a broadcast stream

list_campaigns get_campaign

Campaigns and their statistics

create_campaign_draft

Write a campaign without sending it

send_campaign_now

Sends now: creates a campaign and mails the stream

update_campaign send_campaign cancel_campaign

Edit, send or call off a campaign

list_subscribers add_subscriber import_subscribers

The audience of a broadcast stream

record_complaint remove_subscriber

Suppress or remove an address

list_layouts get_layout create_layout update_layout delete_layout

Template layouts

list_inbound get_inbound retry_inbound bypass_inbound

Inbound and held messages

list_api_requests list_tags

The server's request log and tag index

Which campaign tool sends

There are two ways to create a campaign and they behave differently:

  • create_campaign_draft writes it and waits. Without scheduled_at it stays a draft; with one the server sends it when due.

  • send_campaign_now creates it and mails every subscriber of the stream before the call returns. There is no draft to review.

They are separate tools because they are separate API routes, and calling one when you meant the other is the difference between a draft and a broadcast.

Tools that mail people or remove data carry the MCP destructiveHint annotation; the read-only ones carry readOnlyHint. A client can use those to ask before running one.

Example prompts:

Send a plain-text email from billing@acme.com to ada@example.com thanking her for the purchase.

Why did yesterday's emails to @gmail.com addresses bounce?

Draft a September newsletter for the product-news stream, but do not send it yet.

How many people are subscribed to product-news, and how did last month's campaign do?

Errors

API failures come back as tool errors carrying the stable Camelmailer error code (Unauthorized, NotFound, ValidationError, …), so the assistant can react — nothing crashes the server.

Docs

Full API reference: camelmailer.com/docs · SDK: camelmailer-node · CLI: camelmailer-cli

License

MIT

Available Tools

38 tools
add_subscriberA

Add or update one subscriber of a broadcast stream. Upserts by address, so calling it twice is safe.

Inputs: address (required), permalink (required), status.

archive_streamA
Destructive

Archive a message stream. Archived streams reject new messages.

Inputs: permalink (required).

bypass_inboundA
Destructive

RELEASE A HELD MESSAGE past the hold and deliver it. The hold is what the spam filter put there, so check the message before releasing it.

Inputs: id (required).

cancel_campaignA
Destructive

Cancel a scheduled or in-flight campaign. Messages already queued are not recalled.

Inputs: id (required).

create_campaign_draftA

Write a campaign WITHOUT sending it. Leave scheduled_at unset and the campaign stays a draft; set it and the server sends when due. This is the tool to use when a campaign should be reviewed first — use send_campaign_now only when it should go out immediately.

Inputs: from (required), stream (required), name, subject, +3 more.

create_layoutA

Create a template layout. html_wrapper has to embed the body with {{{ content }}}; anything else is refused with ValidationError.

Inputs: name (required), html_wrapper (required), permalink, text_wrapper.

create_streamA

Create a message stream. Set permalink explicitly when you need to know it up front; the API derives one from the name otherwise.

Inputs: name (required), permalink, stream_type.

delete_layoutA
Destructive

Delete a layout. Templates that referenced it fall back to no wrapper.

Inputs: permalink (required).

dmarc_summaryA
Read-only

DMARC compliance summary over the stored aggregate reports: pass rate, top sending sources and disposition totals.

Inputs: to, from, domain.

get_campaignA
Read-only

Retrieve one campaign with its statistics: total, sent, delivered, failed, opened, clicked and unsubscribed.

Inputs: id (required).

get_emailA
Read-only

Retrieve one message by id, including its SMTP delivery attempts.

Inputs: id (required).

get_inboundA
Read-only

Retrieve one inbound or held message by id.

Inputs: id (required).

get_layoutA
Read-only

Retrieve one layout by permalink, including its wrappers.

Inputs: permalink (required).

get_statsB
Read-only

Message counters of the server (sent, pending, bounced, opens, clicks, …), optionally limited to a created_at time window.

Inputs: to, from.

get_streamA
Read-only

Retrieve one message stream by permalink.

Inputs: permalink (required).

import_subscribersA

Add many addresses to a broadcast stream at once, all as subscribed. Blanks and duplicates within the request are skipped, so the reported count can be lower than the number of addresses passed.

Inputs: addresses (required), permalink (required).

list_api_requestsA
Read-only

List the server's own logged API requests, newest first. Useful when a send did not arrive and the question is whether the request ever reached the API, and with what answer.

Inputs: to, from, page, method, +2 more.

list_bouncesC
Read-only

List bounced messages, filtered and paginated.

Inputs: tag, page, query, status, +1 more.

list_campaignsA
Read-only

List broadcast campaigns, newest first. Pass stream to narrow to one broadcast stream.

Inputs: stream.

list_emailsA
Read-only

List messages of the CamelMailer server, newest first. Filter by scope, status, tag, substring query or message stream.

Inputs: tag, page, query, scope, +3 more.

list_inboundA
Read-only

List inbound and held messages, newest first. Covers mail arriving through an inbound route as well as outbound mail the spam filter put on hold.

Inputs: page, query, status, stream, +1 more.

list_layoutsA
Read-only

List the template layouts of the server. A layout wraps every template that uses it, so header, footer and styling live in one place.

Inputs: no named parameters.

list_streamsA
Read-only

List the message streams of the server. A stream is transactional or broadcast; broadcast streams are the ones campaigns and subscribers belong to.

Inputs: no named parameters.

list_subscribersA
Read-only

List a broadcast stream's subscribers, subscribed and unsubscribed alike. A broadcast send to an address that is not subscribed is refused, so this list is the audience.

Inputs: permalink (required).

list_tagsA
Read-only

Tags used by the server's recent messages, most used first — the vocabulary available to the tag filter of list_emails.

Inputs: no named parameters.

list_templatesA
Read-only

List all stored message templates of the CamelMailer server.

Inputs: no named parameters.

record_complaintA
Destructive

Record a spam complaint against an address: writes a stream-scoped suppression and flips the subscription to unsubscribed. Idempotent, so a feedback loop can replay it safely.

Inputs: address (required), permalink (required).

remove_subscriberA
Destructive

Remove a subscriber from a broadcast stream entirely. To stop mailing someone while keeping the record, set their status to unsubscribed with add_subscriber instead.

Inputs: address (required), permalink (required).

render_templateA
Read-only

Preview a stored template rendered against a variable model — returns the rendered subject, html_body and text_body without sending anything.

Inputs: template (required), template_model.

retry_inboundA
Destructive

Put an inbound message back on the delivery queue, for instance after fixing the route it should have matched.

Inputs: id (required).

send_campaignA
Destructive

SENDS AN EXISTING CAMPAIGN NOW, whatever its schedule said. The send starts immediately and cannot be undone for messages already queued.

Inputs: id (required).

send_campaign_nowA
Destructive

CREATES A CAMPAIGN AND SENDS IT IMMEDIATELY to every subscriber of the stream. There is no draft to review and no schedule; the send starts before this returns. Use create_campaign_draft unless the mail really should go out now.

Inputs: name (required), permalink (required), from, subject, +2 more.

send_emailA
Destructive

Send a transactional email through CamelMailer. Provide html_body and/or text_body. Queues one message per recipient and returns their ids.

Inputs: to (required), from (required), cc, bcc, +7 more.

send_email_with_templateA
Destructive

Render a stored CamelMailer template (Mustache-style {{ variables }}) against template_model and send it. Fields set directly (e.g. subject) override the rendered ones.

Inputs: to (required), from (required), template (required), cc, +7 more.

send_to_streamA
Destructive

SENDS MAIL IMMEDIATELY to every subscriber of a broadcast stream. Give either a subject with a body, or a template permalink. Recipients past the per-request cap of 1000 come back as skipped, so a larger audience wants a campaign.

Inputs: from (required), permalink (required), subject, template, +3 more.

update_campaignA

Edit a draft or scheduled campaign. Set scheduled_at to schedule it, or clear_schedule to drop it back to a draft. Touching neither leaves the schedule standing. A campaign that is already sending cannot be edited.

Inputs: id (required), from, name, subject, +4 more.

update_layoutB

Update a layout. Only the given fields change.

Inputs: permalink (required), name, html_wrapper, text_wrapper.

update_streamB

Update a message stream. Only the given fields change.

Inputs: permalink (required), name, archived, stream_type.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, and descriptions explicitly disambiguate near-overlaps like send_campaign_now vs send_campaign and send_to_stream vs create_campaign_draft. A few pairs, such as get_email vs get_inbound and list_emails vs list_bounces, could still cause misselection if an agent is not careful.

    Naming Consistency4/5

    The naming is predominantly lowercase snake_case verb_noun, e.g. list_campaigns, create_layout, update_stream, cancel_campaign. Minor deviations like dmarc_summary, send_campaign_now, and send_email_with_template break the exact pattern but remain readable and predictable.

    Tool Count2/5

    At 38 tools, this is well beyond the typical 3-15 tool sweet spot and above the 25-tool threshold for a heavy surface. Although the tools are organized into logical domains, the sheer number makes navigation and selection harder for an agent.

    Completeness3/5

    The surface is broad, covering transactional sends, campaigns, streams, subscribers, layouts, inbound handling, and stats, but template management is read-only: list_templates and render_template exist with no create_template/update_template/delete_template. There are also lifecycle gaps like no delete_campaign, delete_stream, or unarchive_stream.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Lets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send transactional emails through Quolle, including sending, batching, canceling, and checking delivery status of emails.
      6
      23 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to send and track transactional email, manage templates and sending domains, and read inbound email through the transactional email API.
      16
      38 npm
      MIT