MisarMail MCP Server

Official54 toolsLive

by Misar-AI · TypeScript

Send transactional email, run campaigns, manage contacts and automations, audit deliverability.

MisarMail MCP Server (io.github.Misar-AI/misarmail-mcp)

The MisarMail MCP server provides a Model Context Protocol (MCP) integration for sending transactional email, running campaigns, managing contacts and automations, and auditing email deliverability. It also supports A/B testing. The server is intended to be used “from any AI assistant,” with compatibility listed for Claude and multiple editors/agents.

🛠️ Key Features

Transactional email sending
Campaign execution
Contact and automation management
A/B testing
Deliverability audit

🚀 Use Cases

Run email campaigns from an AI assistant
Maintain contact lists and automations
Test variants via A/B testing and review deliverability

⚡ Developer Benefits

MCP server with 54 tools
Listed support for Claude (Desktop, Code, web), Cursor, VS Code, Windsurf, Cline, Zed, and Gemini CLI
README indicates 8 prompts, 4 resources, and 8 agent skills

⚠️ Limitations

Server scope is limited to the email workflows described (transactional email, campaigns, contacts/automations, and deliverability auditing).

Topics

emailmcpmisarmailaiautomationcampaignscontactsdeliverabilityemail-marketingmcp-servermodel-context-protocoltypescriptai-agentclaudecursortransactional-email

Captured live from the server via tools/list.

send_email

Send a transactional email from a verified MisarMail account. `from.email` must match an email account you have already verified — use list_domains to check which sender domains are available. Returns the message ID and queue status.

Parameters12

from	object	required	Sender address (must match a verified MisarMail account)
to	array	required	Recipient list (1–100 addresses)
cc	array	optional	CC recipients (max 50)
bcc	array	optional	BCC recipients (max 50, hidden from other recipients)
reply_to	object	optional	Reply-to address
subject	string	required	Email subject (max 998 chars)
html	string	optional	HTML body (max 500KB, recommended)
text	string	optional	Plain text body (max 500KB, fallback for HTML)
alias_id	string	optional	Route via a specific alias SMTP pool
idempotency_key	string	optional	Unique key to prevent duplicate sends (max 128 chars)
tags	array	optional	Tags for tracking (max 10, each max 64 chars)
metadata	object	optional	Custom metadata key-value pairs (max 20 pairs)

Raw schema

{
  "type": "object",
  "properties": {
    "from": {
      "type": "object",
      "required": [
        "email"
      ],
      "description": "Sender address (must match a verified MisarMail account)",
      "properties": {
        "email": {
          "type": "string",
          "description": "Sender email address"
        },
        "name": {
          "type": "string",
          "description": "Sender display name shown to recipients"
        }
      }
    },
    "to": {
      "type": "array",
      "description": "Recipient list (1–100 addresses)",
      "items": {
        "type": "object",
        "required": [
          "email"
        ],
        "properties": {
          "email": {
            "type": "string",
            "description": "Recipient email address"
          },
          "name": {
            "type": "string",
            "description": "Recipient display name"
          }
        }
      }
    },
    "cc": {
      "type": "array",
      "description": "CC recipients (max 50)",
      "items": {
        "type": "object",
        "required": [
          "email"
        ],
        "properties": {
          "email": {
            "type": "string",
            "description": "Recipient email address"
          },
          "name": {
            "type": "string",
            "description": "Recipient display name"
          }
        }
      }
    },
    "bcc": {
      "type": "array",
      "description": "BCC recipients (max 50, hidden from other recipients)",
      "items": {
        "type": "object",
        "required": [
          "email"
        ],
        "properties": {
          "email": {
            "type": "string",
            "description": "Recipient email address"
          },
          "name": {
            "type": "string",
            "description": "Recipient display name"
          }
        }
      }
    },
    "reply_to": {
      "type": "object",
      "description": "Reply-to address",
      "properties": {
        "email": {
          "type": "string"
        },
        "name": {
          "type": "string"
        }
      }
    },
    "subject": {
      "type": "string",
      "description": "Email subject (max 998 chars)"
    },
    "html": {
      "type": "string",
      "description": "HTML body (max 500KB, recommended)"
    },
    "text": {
      "type": "string",
      "description": "Plain text body (max 500KB, fallback for HTML)"
    },
    "alias_id": {
      "type": "string",
      "description": "Route via a specific alias SMTP pool"
    },
    "idempotency_key": {
      "type": "string",
      "description": "Unique key to prevent duplicate sends (max 128 chars)"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags for tracking (max 10, each max 64 chars)"
    },
    "metadata": {
      "type": "object",
      "description": "Custom metadata key-value pairs (max 20 pairs)"
    }
  },
  "required": [
    "from",
    "to",
    "subject"
  ]
}

list_emails

List emails from a mailbox folder with optional full-text search across subject and body. Use this for reading the unified inbox; use list_campaigns for marketing sends.

Parameters3

folder	string	optional	Folder to list (default: inbox)
limit	number	optional	Number of emails to return (default 20, max 50)
search	string	optional	Search query across subject and body

Raw schema

{
  "type": "object",
  "properties": {
    "folder": {
      "type": "string",
      "enum": [
        "inbox",
        "sent",
        "drafts",
        "archive",
        "spam",
        "trash",
        "starred"
      ],
      "description": "Folder to list (default: inbox)"
    },
    "limit": {
      "type": "number",
      "description": "Number of emails to return (default 20, max 50)"
    },
    "search": {
      "type": "string",
      "description": "Search query across subject and body"
    }
  }
}

get_email

Read the full content of a single email by ID, including headers, body, and attachments metadata. Side effect: marks the email as read.

Parameters1

string

required

Email ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Email ID (UUID)"
    }
  },
  "required": [
    "id"
  ]
}

reply_to_email

Reply to an existing email thread. The sender address and threading headers are derived from the original message, so only the body is required.

Parameters3

email_id	string	required	ID of the email to reply to
html	string	optional	HTML reply body
text	string	optional	Plain text reply body

Raw schema

{
  "type": "object",
  "properties": {
    "email_id": {
      "type": "string",
      "description": "ID of the email to reply to"
    },
    "html": {
      "type": "string",
      "description": "HTML reply body"
    },
    "text": {
      "type": "string",
      "description": "Plain text reply body"
    }
  },
  "required": [
    "email_id"
  ]
}

archive_email

Move one email out of the inbox and into the archive. Use it to clear handled mail from the working inbox. This is REVERSIBLE and non-destructive: the message is not deleted, its content is unchanged, and it can be found again through the archive. It does not mark the message read, reply to it, or notify the sender. Safe to repeat — archiving an already-archived email changes nothing. Requires an API key. Affects exactly one message per call.

Parameters1

string

required

Email ID to archive

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Email ID to archive"
    }
  },
  "required": [
    "id"
  ]
}

validate_email

Validate an email address before sending: syntax, MX records, disposable-domain and role-account detection. Use this to protect sender reputation on imported lists.

Parameters1

string

required

Email address to validate

Raw schema

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "Email address to validate"
    }
  },
  "required": [
    "email"
  ]
}

list_campaigns

List email marketing campaigns with their status, audience size, and headline metrics. Filter by status to find drafts ready to send or campaigns still sending.

Parameters3

status	string	optional	Filter by campaign status
page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20, max 100)

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "draft",
        "scheduled",
        "sending",
        "sent",
        "paused",
        "failed"
      ],
      "description": "Filter by campaign status"
    },
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20, max 100)"
    }
  }
}

get_campaign

Get full details for one campaign: content, audience segment, schedule, and delivery statistics (sent, opened, clicked, bounced, complained).

Parameters1

campaign_id

string

required

Campaign ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "campaign_id": {
      "type": "string",
      "description": "Campaign ID (UUID)"
    }
  },
  "required": [
    "campaign_id"
  ]
}

create_campaign

Create a new email marketing campaign as a draft. Creating never sends — call send_campaign separately once the content and audience are confirmed.

Parameters11

name	string	required	Internal campaign name (not shown to recipients)
subject	string	required	Subject line recipients will see
from_email	string	required	Verified sender address
from_name	string	optional	Sender display name
reply_to	string	optional	Reply-to address
html	string	optional	HTML body content
text	string	optional	Plain text body content
template_id	string	optional	Use a saved template instead of inline HTML
segment_id	string	optional	Audience segment to send to
tags	array	optional	Contact tags to target
scheduled_at	string	optional	ISO 8601 timestamp to schedule the send (omit to keep as draft)

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Internal campaign name (not shown to recipients)"
    },
    "subject": {
      "type": "string",
      "description": "Subject line recipients will see"
    },
    "from_email": {
      "type": "string",
      "description": "Verified sender address"
    },
    "from_name": {
      "type": "string",
      "description": "Sender display name"
    },
    "reply_to": {
      "type": "string",
      "description": "Reply-to address"
    },
    "html": {
      "type": "string",
      "description": "HTML body content"
    },
    "text": {
      "type": "string",
      "description": "Plain text body content"
    },
    "template_id": {
      "type": "string",
      "description": "Use a saved template instead of inline HTML"
    },
    "segment_id": {
      "type": "string",
      "description": "Audience segment to send to"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Contact tags to target"
    },
    "scheduled_at": {
      "type": "string",
      "description": "ISO 8601 timestamp to schedule the send (omit to keep as draft)"
    }
  },
  "required": [
    "name",
    "subject",
    "from_email"
  ]
}

send_campaign

Send a campaign now, or schedule it for a future time by passing scheduled_at. This delivers real email to real recipients and cannot be undone once sending starts — confirm the audience with get_campaign first.

Parameters2

campaign_id	string	required	Campaign ID (UUID)
scheduled_at	string	optional	ISO 8601 timestamp to schedule instead of sending immediately

Raw schema

{
  "type": "object",
  "properties": {
    "campaign_id": {
      "type": "string",
      "description": "Campaign ID (UUID)"
    },
    "scheduled_at": {
      "type": "string",
      "description": "ISO 8601 timestamp to schedule instead of sending immediately"
    }
  },
  "required": [
    "campaign_id"
  ]
}

list_contacts

List contacts with their subscription status and engagement metrics. Filter by status to find unsubscribed or bounced addresses that should be excluded from sends.

Parameters4

status	string	optional	Filter by subscription status
search	string	optional	Search across email, name, and company
page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20, max 100)

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "subscribed",
        "unsubscribed",
        "bounced",
        "complained"
      ],
      "description": "Filter by subscription status"
    },
    "search": {
      "type": "string",
      "description": "Search across email, name, and company"
    },
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20, max 100)"
    }
  }
}

create_contact

Add a single contact. Adding a contact records consent to email them — only add addresses that opted in, or the send will damage sender reputation and may breach CAN-SPAM/GDPR.

Parameters9

email	string	required	Contact email address
first_name	string	optional	First name (max 100 chars)
last_name	string	optional	Last name (max 100 chars)
phone	string	optional	Phone number (max 50 chars)
company	string	optional	Company name (max 150 chars)
job_title	string	optional	Job title (max 100 chars)
tags	array	optional	Segmentation tags
source	string	optional	Where this contact came from (max 100 chars)
custom_fields	object	optional	Custom key-value attributes

Raw schema

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "Contact email address"
    },
    "first_name": {
      "type": "string",
      "description": "First name (max 100 chars)"
    },
    "last_name": {
      "type": "string",
      "description": "Last name (max 100 chars)"
    },
    "phone": {
      "type": "string",
      "description": "Phone number (max 50 chars)"
    },
    "company": {
      "type": "string",
      "description": "Company name (max 150 chars)"
    },
    "job_title": {
      "type": "string",
      "description": "Job title (max 100 chars)"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Segmentation tags"
    },
    "source": {
      "type": "string",
      "description": "Where this contact came from (max 100 chars)"
    },
    "custom_fields": {
      "type": "object",
      "description": "Custom key-value attributes"
    }
  },
  "required": [
    "email"
  ]
}

update_contact

Update an existing contact by email address, including changing subscription status. Setting status to unsubscribed immediately excludes them from every future campaign.

Parameters9

email	string	required	Email address identifying the contact
first_name	string	optional	First name
last_name	string	optional	Last name
phone	string	optional	Phone number
company	string	optional	Company name
job_title	string	optional	Job title
status	string	optional	New subscription status
tags	array	optional	Replace segmentation tags
custom_fields	object	optional	Custom key-value attributes to merge

Raw schema

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "Email address identifying the contact"
    },
    "first_name": {
      "type": "string",
      "description": "First name"
    },
    "last_name": {
      "type": "string",
      "description": "Last name"
    },
    "phone": {
      "type": "string",
      "description": "Phone number"
    },
    "company": {
      "type": "string",
      "description": "Company name"
    },
    "job_title": {
      "type": "string",
      "description": "Job title"
    },
    "status": {
      "type": "string",
      "enum": [
        "subscribed",
        "unsubscribed",
        "bounced",
        "complained"
      ],
      "description": "New subscription status"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Replace segmentation tags"
    },
    "custom_fields": {
      "type": "object",
      "description": "Custom key-value attributes to merge"
    }
  },
  "required": [
    "email"
  ]
}

import_contacts

Bulk-import up to 5,000 contacts in one call. Existing addresses are updated rather than duplicated. Returns per-row results so you can see which rows were rejected and why.

Parameters2

contacts	array	required	Contacts to import (max 5000)
update_existing	boolean	optional	Update contacts that already exist (default true)

Raw schema

{
  "type": "object",
  "properties": {
    "contacts": {
      "type": "array",
      "description": "Contacts to import (max 5000)",
      "items": {
        "type": "object",
        "required": [
          "email"
        ],
        "properties": {
          "email": {
            "type": "string"
          },
          "first_name": {
            "type": "string"
          },
          "last_name": {
            "type": "string"
          },
          "company": {
            "type": "string"
          },
          "tags": {
            "type": "array",
            "items": {
              "type": "string"
            }
          }
        }
      }
    },
    "update_existing": {
      "type": "boolean",
      "description": "Update contacts that already exist (default true)"
    }
  },
  "required": [
    "contacts"
  ]
}

get_contact_score

Get engagement score, engagement tier, and churn risk for one contact — or the lowest-engagement contacts across the list when contact_id is omitted. Use before a re-engagement campaign.

Parameters1

contact_id

string

optional

Contact ID to score (omit to return the lowest-engagement contacts)

Raw schema

{
  "type": "object",
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "Contact ID to score (omit to return the lowest-engagement contacts)"
    }
  }
}

list_templates

List the saved email templates on the account, with the variable placeholders each one expects. Use it to pick a template before composing a send, and to see which variables you must supply — a template rendered with a missing variable goes out with a visible gap. These are the account's own templates; list_marketplace_items covers third-party ones instead. Reads only; no template is created, edited, or sent. Requires an API key. An empty list means none have been saved yet, which is not an error.

Parameters3

type	string	optional	Filter by template type
page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20)

Raw schema

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "transactional",
        "marketing",
        "automation"
      ],
      "description": "Filter by template type"
    },
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20)"
    }
  }
}

create_template

Create a reusable email template. Use {{variable}} placeholders for personalisation — they are substituted at send time and previewable via render_template.

Parameters6

name	string	required	Template name
subject	string	required	Default subject line (supports {{variables}})
html	string	required	HTML body (supports {{variables}})
text	string	optional	Plain text fallback body
type	string	optional	Template type (default: marketing)
variables	array	optional	Declared variable names used in the template

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Template name"
    },
    "subject": {
      "type": "string",
      "description": "Default subject line (supports {{variables}})"
    },
    "html": {
      "type": "string",
      "description": "HTML body (supports {{variables}})"
    },
    "text": {
      "type": "string",
      "description": "Plain text fallback body"
    },
    "type": {
      "type": "string",
      "enum": [
        "transactional",
        "marketing",
        "automation"
      ],
      "description": "Template type (default: marketing)"
    },
    "variables": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Declared variable names used in the template"
    }
  },
  "required": [
    "name",
    "subject",
    "html"
  ]
}

render_template

Render a template with sample variables and return the resulting HTML and subject. Use this to preview personalisation before sending anything.

Parameters2

template_id	string	required	Template ID to render
variables	object	optional	Variable values to substitute, e.g. { "first_name": "Ada" }

Raw schema

{
  "type": "object",
  "properties": {
    "template_id": {
      "type": "string",
      "description": "Template ID to render"
    },
    "variables": {
      "type": "object",
      "description": "Variable values to substitute, e.g. { \"first_name\": \"Ada\" }"
    }
  },
  "required": [
    "template_id"
  ]
}

list_automations

List automation workflows on the account — welcome series, re-engagement, drip sequences — with their status and enrolment counts. Use it to see what is running before adding another workflow that might overlap, and to find an automation id for get_automation or toggle_automation. Listing does not reveal the individual steps; get_automation does that. Reads only; nothing is activated, paused, or enrolled. Requires an API key. An automation may exist while inactive, so read the status rather than assuming a listed workflow is sending.

Parameters3

status	string	optional	Filter by automation status
page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20)

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "active",
        "paused",
        "draft"
      ],
      "description": "Filter by automation status"
    },
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20)"
    }
  }
}

get_automation

Get one automation workflow in full: its trigger, every step with its settings, and current enrolment counts. Use it to understand exactly what an automation will do to contacts before activating it — the step list is where sends, waits and branches become visible. For the list of automations, use list_automations; to start or pause one, toggle_automation. Reads only; reading a workflow does not enrol anyone or trigger a step. Requires an API key. An automation can be defined but inactive, so check its state rather than assuming it is running.

Parameters1

automation_id

string

required

Automation ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "automation_id": {
      "type": "string",
      "description": "Automation ID (UUID)"
    }
  },
  "required": [
    "automation_id"
  ]
}

create_automation

Create an automation workflow from a trigger and an ordered list of steps. Created paused by default — call toggle_automation to activate once the steps are reviewed.

Parameters5

name	string	required	Automation name
trigger	string	required	Event that starts the workflow
trigger_config	object	optional	Trigger parameters, e.g. { "tag": "trial" } for tag_added
steps	array	optional	Ordered workflow steps
active	boolean	optional	Start active immediately (default false)

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Automation name"
    },
    "trigger": {
      "type": "string",
      "enum": [
        "contact_created",
        "tag_added",
        "campaign_opened",
        "link_clicked",
        "date_based"
      ],
      "description": "Event that starts the workflow"
    },
    "trigger_config": {
      "type": "object",
      "description": "Trigger parameters, e.g. { \"tag\": \"trial\" } for tag_added"
    },
    "steps": {
      "type": "array",
      "description": "Ordered workflow steps",
      "items": {
        "type": "object",
        "required": [
          "type"
        ],
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "send_email",
              "wait",
              "add_tag",
              "remove_tag",
              "condition"
            ],
            "description": "Step action"
          },
          "delay_hours": {
            "type": "number",
            "description": "Hours to wait before this step"
          },
          "template_id": {
            "type": "string",
            "description": "Template for send_email steps"
          },
          "subject": {
            "type": "string",
            "description": "Subject for send_email steps"
          },
          "tag": {
            "type": "string",
            "description": "Tag for add_tag / remove_tag steps"
          }
        }
      }
    },
    "active": {
      "type": "boolean",
      "description": "Start active immediately (default false)"
    }
  },
  "required": [
    "name",
    "trigger"
  ]
}

toggle_automation

Activate or pause one automation workflow. This is consequential in one direction: ACTIVATING starts enrolling contacts, which means real emails begin going out on the workflow's schedule without further confirmation. Pausing stops new enrolments. Read the workflow with get_automation first so you know what activating will actually send. Contacts already part-way through a paused workflow are held rather than dropped, so pausing is not a cancellation. Safe to repeat. Requires an API key.

Parameters2

automation_id	string	required	Automation ID (UUID)
active	boolean	required	true to activate, false to pause

Raw schema

{
  "type": "object",
  "properties": {
    "automation_id": {
      "type": "string",
      "description": "Automation ID (UUID)"
    },
    "active": {
      "type": "boolean",
      "description": "true to activate, false to pause"
    }
  },
  "required": [
    "automation_id",
    "active"
  ]
}

list_ab_tests

List A/B tests on the account with each variant's results and whether a winner has been picked yet. Use it to see which tests are still running and which are waiting on a decision. Reading results here is safe and has no effect on the test — declaring a winner is a separate, irreversible action that sends to the held-back audience. Reads only. Requires an API key. A test with no winner selected is still open; treat early results with care, since a lead that looks decisive on a small sample often is not.

Parameters3

type	string	optional	Filter by what is being tested
page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20)

Raw schema

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "subject",
        "content",
        "send_time",
        "from_name"
      ],
      "description": "Filter by what is being tested"
    },
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20)"
    }
  }
}

create_ab_test

Create an A/B test on a campaign with two or more variants. A sample percentage is sent first; the winner goes to the remainder once selected.

Parameters5

campaign_id	string	required	Campaign to test
type	string	required	What to test
variants	array	required	Test variants (2–5)
sample_percentage	number	optional	Percent of the audience used for the test (default 20)
winner_metric	string	optional	Metric used to pick the winner (default open_rate)

Raw schema

{
  "type": "object",
  "properties": {
    "campaign_id": {
      "type": "string",
      "description": "Campaign to test"
    },
    "type": {
      "type": "string",
      "enum": [
        "subject",
        "content",
        "send_time",
        "from_name"
      ],
      "description": "What to test"
    },
    "variants": {
      "type": "array",
      "description": "Test variants (2–5)",
      "items": {
        "type": "object",
        "properties": {
          "label": {
            "type": "string",
            "description": "Variant label, e.g. A / B"
          },
          "subject": {
            "type": "string",
            "description": "Subject line for subject tests"
          },
          "html": {
            "type": "string",
            "description": "Body content for content tests"
          },
          "from_name": {
            "type": "string",
            "description": "Sender name for from_name tests"
          },
          "send_at": {
            "type": "string",
            "description": "ISO timestamp for send_time tests"
          }
        }
      }
    },
    "sample_percentage": {
      "type": "number",
      "description": "Percent of the audience used for the test (default 20)"
    },
    "winner_metric": {
      "type": "string",
      "enum": [
        "open_rate",
        "click_rate",
        "conversion_rate"
      ],
      "description": "Metric used to pick the winner (default open_rate)"
    }
  },
  "required": [
    "campaign_id",
    "type",
    "variants"
  ]
}

select_ab_test_winner

Select the winning variant and send it to the remaining audience. This triggers a real send to everyone who was held back — it cannot be undone.

Parameters3

test_id	string	required	A/B test ID
winner_variant	string	required	Label of the winning variant, e.g. B
metric	string	optional	Metric the decision was based on (default open_rate)

Raw schema

{
  "type": "object",
  "properties": {
    "test_id": {
      "type": "string",
      "description": "A/B test ID"
    },
    "winner_variant": {
      "type": "string",
      "description": "Label of the winning variant, e.g. B"
    },
    "metric": {
      "type": "string",
      "enum": [
        "open_rate",
        "click_rate",
        "conversion_rate"
      ],
      "description": "Metric the decision was based on (default open_rate)"
    }
  },
  "required": [
    "test_id",
    "winner_variant"
  ]
}

get_analytics

Get delivery and engagement analytics — sent, delivered, opened, clicked, bounced, and complained — for the account or one campaign, grouped by day/week/month.

Parameters5

campaign_id	string	optional	Limit to one campaign (omit for account-wide)
start_date	string	optional	Start date, ISO 8601 (e.g. 2026-01-01)
end_date	string	optional	End date, ISO 8601
period	string	optional	Shorthand window used when start_date is omitted (default 30d)
group_by	string	optional	Time bucket for the series (default day)

Raw schema

{
  "type": "object",
  "properties": {
    "campaign_id": {
      "type": "string",
      "description": "Limit to one campaign (omit for account-wide)"
    },
    "start_date": {
      "type": "string",
      "description": "Start date, ISO 8601 (e.g. 2026-01-01)"
    },
    "end_date": {
      "type": "string",
      "description": "End date, ISO 8601"
    },
    "period": {
      "type": "string",
      "enum": [
        "today",
        "7d",
        "30d",
        "90d"
      ],
      "description": "Shorthand window used when start_date is omitted (default 30d)"
    },
    "group_by": {
      "type": "string",
      "enum": [
        "day",
        "week",
        "month"
      ],
      "description": "Time bucket for the series (default day)"
    }
  }
}

generate_report

Generate a structured analytics report over a date range. Report types: campaign_performance, engagement_funnel, cohort_analysis, and send_time_heatmap (best hour/day to send).

Parameters3

report_type	string	required	Type of report to generate
date_from	string	optional	Start date, ISO 8601 (default: 30 days ago)
date_to	string	optional	End date, ISO 8601 (default: today)

Raw schema

{
  "type": "object",
  "properties": {
    "report_type": {
      "type": "string",
      "enum": [
        "campaign_performance",
        "engagement_funnel",
        "cohort_analysis",
        "send_time_heatmap"
      ],
      "description": "Type of report to generate"
    },
    "date_from": {
      "type": "string",
      "description": "Start date, ISO 8601 (default: 30 days ago)"
    },
    "date_to": {
      "type": "string",
      "description": "End date, ISO 8601 (default: today)"
    }
  },
  "required": [
    "report_type"
  ]
}

get_revenue_attribution

Attribute ecommerce revenue to email — revenue per campaign, per contact, and average order value from tracked conversions.

Parameters2

period	string	optional	Time window (default 30d)
campaign_id	string	optional	Limit to one campaign

Raw schema

{
  "type": "object",
  "properties": {
    "period": {
      "type": "string",
      "enum": [
        "today",
        "7d",
        "30d",
        "90d"
      ],
      "description": "Time window (default 30d)"
    },
    "campaign_id": {
      "type": "string",
      "description": "Limit to one campaign"
    }
  }
}

get_monetization_stats

Get newsletter monetization figures: paid subscribers, monthly recurring revenue, churn, and revenue trend. Use it for 'how is the paid newsletter doing' questions. These are account-level totals over a trailing window, so they cannot be broken down per campaign — use get_revenue_attribution for that. Reads only; no billing state is changed and no subscriber is charged. Requires an API key. Revenue figures are reported in minor currency units unless stated otherwise, so check before presenting them as dollars. Zero paid subscribers is a real answer.

Parameters1

period

string

optional

Time window (default 30d)

Raw schema

{
  "type": "object",
  "properties": {
    "period": {
      "type": "string",
      "enum": [
        "today",
        "7d",
        "30d",
        "90d"
      ],
      "description": "Time window (default 30d)"
    }
  }
}

get_deliverability_score

Get the account deliverability score (0–100) and letter grade (A–F) with the factors dragging it down. Start here when asked why emails are landing in spam.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

run_deliverability_audit

Run a full deliverability audit across authentication (SPF/DKIM/DMARC), domain reputation, list hygiene, content signals, and blocklist status. Returns prioritized findings.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

get_warmup_status

Get IP/domain warm-up progress and today's remaining send capacity. Exceeding warm-up capacity on a new domain is the fastest way to get throttled or blocklisted.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

check_dmarc

Check live SPF, DKIM, and DMARC DNS records for a domain and report alignment problems with the exact record to publish. Works for any domain, not only your own.

Parameters1

domain

string

required

Domain to check, e.g. example.com

Raw schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain to check, e.g. example.com"
    }
  },
  "required": [
    "domain"
  ]
}

list_domains

List sending domains with verification status and their DKIM/SPF/DMARC records. Check here first when a send fails with an unverified-sender error.

Parameters2

page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20)

Raw schema

{
  "type": "object",
  "properties": {
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20)"
    }
  }
}

add_domain

Add a sending domain and return the DNS records to publish. The domain cannot send until those records are live and verify_domain succeeds.

Parameters1

domain

string

required

Domain to add, e.g. example.com

Raw schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain to add, e.g. example.com"
    }
  },
  "required": [
    "domain"
  ]
}

verify_domain

Re-check a domain's DNS records and mark it verified if they resolve. Safe to retry — DNS propagation can take up to 48 hours.

Parameters1

domain_id

string

required

Domain ID returned by add_domain

Raw schema

{
  "type": "object",
  "properties": {
    "domain_id": {
      "type": "string",
      "description": "Domain ID returned by add_domain"
    }
  },
  "required": [
    "domain_id"
  ]
}

configure_inbound_domain

Configure inbound email routing for a subdomain so replies land in the MisarMail unified inbox. Returns the MX record to publish.

Parameters3

domain	string	required	Root domain, e.g. example.com
subdomain	string	required	Inbound subdomain label, e.g. reply
webhook_url	string	optional	Optional HTTPS URL to POST inbound messages to

Raw schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Root domain, e.g. example.com"
    },
    "subdomain": {
      "type": "string",
      "description": "Inbound subdomain label, e.g. reply"
    },
    "webhook_url": {
      "type": "string",
      "description": "Optional HTTPS URL to POST inbound messages to"
    }
  },
  "required": [
    "domain",
    "subdomain"
  ]
}

list_forms

List signup forms on the account with their embed status and conversion counts. Use it to find a form id before get_form or get_form_submissions, and to compare how forms are performing against each other. It returns the forms themselves, not the people who filled them in — that is get_form_submissions. Reads only; no form is created, published, or unpublished. Requires an API key. A form that exists is not necessarily embedded anywhere, so a zero conversion count may mean it was never installed rather than that it converts badly.

Parameters3

status	string	optional	Filter by form status
page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20)

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "active",
        "inactive"
      ],
      "description": "Filter by form status"
    },
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20)"
    }
  }
}

get_form

Get one signup form in full: its fields, its embed code, and where it redirects after submission. Use it when you need the embed snippet to install the form, or need to know which fields it collects before interpreting submissions. For the submitted data itself, use get_form_submissions; for the list of forms, list_forms. Reads only; the form is not modified and no submission is created. Requires an API key. The embed code is meant to be pasted into a site, so returning it does not publish anything by itself.

Parameters1

form_id

string

required

Form ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "form_id": {
      "type": "string",
      "description": "Form ID (UUID)"
    }
  },
  "required": [
    "form_id"
  ]
}

get_form_submissions

List the submissions a signup form has received, including the values entered in each field. Use it to see who signed up and what they told you. This returns PERSONAL DATA — email addresses and whatever else the form collects — so handle it accordingly and do not paste it into shared transcripts. For the form's own definition, use get_form. Reads only; submissions are not deleted, and nobody is subscribed or emailed as a result. Requires an API key. No submissions is a normal answer, not an error.

Parameters3

form_id	string	required	Form ID (UUID)
page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20)

Raw schema

{
  "type": "object",
  "properties": {
    "form_id": {
      "type": "string",
      "description": "Form ID (UUID)"
    },
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20)"
    }
  },
  "required": [
    "form_id"
  ]
}

create_landing_page

Create a hosted landing page with an email capture form. Returns the public URL; subscribers flow straight into your contact list.

Parameters6

name	string	required	Internal page name
headline	string	required	Headline shown to visitors
subheadline	string	optional	Supporting line under the headline
cta_text	string	optional	Call-to-action button text
slug	string	optional	URL slug (auto-generated when omitted)
tags	array	optional	Tags applied to contacts who sign up here

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Internal page name"
    },
    "headline": {
      "type": "string",
      "description": "Headline shown to visitors"
    },
    "subheadline": {
      "type": "string",
      "description": "Supporting line under the headline"
    },
    "cta_text": {
      "type": "string",
      "description": "Call-to-action button text"
    },
    "slug": {
      "type": "string",
      "description": "URL slug (auto-generated when omitted)"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags applied to contacts who sign up here"
    }
  },
  "required": [
    "name",
    "headline"
  ]
}

list_marketplace_items

Browse the MisarMail marketplace for ready-made email and automation templates. Use it to find a starting point instead of authoring from scratch. This is browse only: it installs nothing, and no template is added to the account by listing it. Inspect a candidate with get_marketplace_item before adopting it. Reads only. Requires an API key. Listings are third-party authored, so quality varies. For templates the account already owns, use list_templates instead — these two return different things.

Parameters4

category	string	optional	Filter by category, e.g. newsletter, ecommerce
search	string	optional	Search marketplace listings
page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20)

Raw schema

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "description": "Filter by category, e.g. newsletter, ecommerce"
    },
    "search": {
      "type": "string",
      "description": "Search marketplace listings"
    },
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20)"
    }
  }
}

get_marketplace_item

Get one marketplace listing in full, with its preview, author, and installation instructions. Use it after list_marketplace_items to inspect a template before adopting it — this is the read step, and it does NOT install anything into the account or create a template. Nothing changes until you act on the instructions it returns. Reads only. Requires an API key. Marketplace items are authored by third parties, so review the preview before recommending one; the listing describes what the author claims, not something MisarMail has verified.

Parameters1

item_id

string

required

Marketplace item ID

Raw schema

{
  "type": "object",
  "properties": {
    "item_id": {
      "type": "string",
      "description": "Marketplace item ID"
    }
  },
  "required": [
    "item_id"
  ]
}

list_inbox_conversations

List unified-inbox conversations (threads) with their status and detected intent. Use this for triage; use list_emails for individual messages in a folder.

Parameters6

status	string	optional	Filter by conversation status
intent	string	optional	Filter by detected intent, e.g. interested, unsubscribe, question
channel	string	optional	Filter by channel, e.g. email
q	string	optional	Free-text search across the thread
limit	number	optional	Results to return (default 20)
offset	number	optional	Offset for pagination

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "open",
        "pending",
        "closed"
      ],
      "description": "Filter by conversation status"
    },
    "intent": {
      "type": "string",
      "description": "Filter by detected intent, e.g. interested, unsubscribe, question"
    },
    "channel": {
      "type": "string",
      "description": "Filter by channel, e.g. email"
    },
    "q": {
      "type": "string",
      "description": "Free-text search across the thread"
    },
    "limit": {
      "type": "number",
      "description": "Results to return (default 20)"
    },
    "offset": {
      "type": "number",
      "description": "Offset for pagination"
    }
  }
}

get_inbox_conversation_messages

Get every message in one inbox conversation, oldest first, with sender and timestamp. Use it to read a thread in full before replying or summarising — it is the detail view behind a conversation listing. It covers one conversation, and it does not send, reply, or mark anything as read. Reads only. Requires an API key. Message bodies are real customer correspondence, so treat the contents as confidential. Returns the whole thread rather than a page, so long conversations return a lot of text.

Parameters1

conversation_id

string

required

Conversation ID (UUID)

Raw schema

{
  "type": "object",
  "properties": {
    "conversation_id": {
      "type": "string",
      "description": "Conversation ID (UUID)"
    }
  },
  "required": [
    "conversation_id"
  ]
}

categorize_inbox_emails

Run AI categorisation over a batch of inbox emails to label intent and priority. Consumes AI credits — pass only the emails you actually need triaged.

Parameters1

email_ids

array

required

Email IDs to categorise (max 50 per call)

Raw schema

{
  "type": "object",
  "properties": {
    "email_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Email IDs to categorise (max 50 per call)"
    }
  },
  "required": [
    "email_ids"
  ]
}

list_api_keys

List the API keys on the account with their scopes and when each was last used. Use it to audit access — to spot keys that are unused, over-scoped, or forgotten. It lists key METADATA only: the secret values are not returned by this or any other tool, so a key that has been lost must be rotated rather than recovered. Reads only; no key is created, revoked, or rotated. Requires an API key. Scope and last-used data is security-relevant, so treat the listing as sensitive even though it contains no secrets.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

generate_subject_lines

Generate AI subject-line variants for a campaign topic, optionally tuned to a tone and audience. Good input for create_ab_test.

Parameters4

topic	string	required	What the email is about
tone	string	optional	Desired tone (default professional)
audience	string	optional	Who the email is for
count	number	optional	How many variants to generate (default 5, max 10)

Raw schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "description": "What the email is about"
    },
    "tone": {
      "type": "string",
      "enum": [
        "professional",
        "friendly",
        "urgent",
        "playful",
        "formal"
      ],
      "description": "Desired tone (default professional)"
    },
    "audience": {
      "type": "string",
      "description": "Who the email is for"
    },
    "count": {
      "type": "number",
      "description": "How many variants to generate (default 5, max 10)"
    }
  },
  "required": [
    "topic"
  ]
}

list_integrations

List every third-party integration connected to the account, with its sync status and when it last ran. Start here when a question involves external data — it tells you which integrations exist and whether they are actually syncing. For one integration's configuration and scopes, follow up with get_integration; to turn one on or off, use toggle_integration. Reads only; nothing is connected, disconnected, or re-synced. Requires an API key. An integration listed as connected can still be failing to sync, so check the status rather than assuming. An empty list means nothing is connected yet, which is not an error.

Parameters2

page	number	optional	Page number (default 1)
limit	number	optional	Results per page (default 20)

Raw schema

{
  "type": "object",
  "properties": {
    "page": {
      "type": "number",
      "description": "Page number (default 1)"
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 20)"
    }
  }
}

get_integration

Get one integration in full: its configuration, the scopes it was granted, and the result of its last sync. Use it to diagnose an integration that list_integrations shows as unhealthy, or to check which scopes were granted before relying on a capability. Covers a single integration — list_integrations gives the overview. Reads only; it does not re-run a sync or change any setting. Requires an API key. The response describes what the integration is permitted to do, which is not the same as what it has successfully done — read the last sync result for that.

Parameters1

integration_id

string

required

Integration ID

Raw schema

{
  "type": "object",
  "properties": {
    "integration_id": {
      "type": "string",
      "description": "Integration ID"
    }
  },
  "required": [
    "integration_id"
  ]
}

toggle_integration

Turn one third-party integration on or off. This changes live behaviour: DISABLING stops all syncing through that integration, so data quietly stops flowing until it is re-enabled. It does not disconnect the integration or revoke its credentials — the connection and its scopes survive, which is why re-enabling picks up where it left off. Safe to repeat: setting an integration to the state it is already in changes nothing. Requires an API key. Call list_integrations first so you know the current state rather than toggling blind.

Parameters2

integration_id	string	required	Integration ID
enabled	boolean	required	true to enable, false to disable

Raw schema

{
  "type": "object",
  "properties": {
    "integration_id": {
      "type": "string",
      "description": "Integration ID"
    },
    "enabled": {
      "type": "boolean",
      "description": "true to enable, false to disable"
    }
  },
  "required": [
    "integration_id",
    "enabled"
  ]
}

list_sandbox_sends

List emails captured by sandbox mode. Sandbox intercepts sends instead of delivering them — use it to verify templates and automations without emailing anyone.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

clear_sandbox

Delete every email captured in the sandbox. The sandbox holds messages intercepted during testing so they are never delivered to real recipients. This DELETES ALL of them and cannot be undone — but it touches only intercepted test mail, never sent campaigns, real inbox messages, contacts, or templates. Takes no parameters and offers no filter: it is all or nothing. Requires an API key. Clearing an already-empty sandbox is harmless. Read anything you still need from the sandbox before calling this.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

upgrade

Show the current MisarMail plan, how much of each quota is left, and what upgrading unlocks. Call it any time — not only after hitting a limit. Set open=true to open the checkout page in the default browser.

Parameters2

open	boolean	optional	Open the upgrade/checkout page in the default browser.
plan	string	optional	Plan slug to open (e.g. 'pro', 'max'). Defaults to the recommended plan.

Raw schema

{
  "type": "object",
  "properties": {
    "open": {
      "type": "boolean",
      "description": "Open the upgrade/checkout page in the default browser."
    },
    "plan": {
      "type": "string",
      "description": "Plan slug to open (e.g. 'pro', 'max'). Defaults to the recommended plan."
    }
  }
}

README.md12 KBView on GitHub

MisarMail MCP Server

Send email, run campaigns, manage contacts and automations, A/B test, and audit deliverability — from any AI assistant.

55 tools · 8 prompts · 4 resources · 8 agent skills

Works with Claude (Desktop, Code, and web), Cursor, VS Code, Windsurf, Cline, Zed, Gemini CLI, ChatGPT, and any other MCP-compatible client — over stdio or Streamable HTTP.

Install

Smithery (recommended)

bash

npx -y @smithery/cli install misar/misarmail-mcp --client claude

Claude Code

bash

claude mcp add misarmail -- npx -y @misarmail/mcp@latest

Manual (any client)

json

{
  "mcpServers": {
    "misarmail": {
      "command": "npx",
      "args": ["-y", "@misarmail/mcp@latest"],
      "env": { "MISARMAIL_API_KEY": "msk_your_key_here" }
    }
  }
}

Ready-made configs for every client live in connectors/.

Remote (no install)

json

{
  "mcpServers": {
    "misarmail": {
      "type": "streamable-http",
      "url": "https://api.misar.io/mail/mcp",
      "headers": { "Authorization": "Bearer msk_your_key_here" }
    }
  }
}

Authentication

Two options — no copy-paste needed for the first:

Browser login. Start the server with no key and run the login tool. It opens the MisarMail consent screen, you review the requested permissions, and the key is delivered straight back and saved to ~/.misarmail/config.json.
API key. Create one at https://mail.misar.io/developers and set MISARMAIL_API_KEY.

Self-hosted instances: set MISARMAIL_BASE_URL.

Tools

Tool	Description
`send_email`	Send a transactional email from a verified MisarMail account.
`list_emails`	List emails from a mailbox folder with optional full-text search across subject and body.
`get_email`	Read the full content of a single email by ID, including headers, body, and attachments metadata.
`reply_to_email`	Reply to an existing email thread.
`archive_email`	Move an email to the archive folder.
`validate_email`	Validate an email address before sending: syntax, MX records, disposable-domain and role-account detection.
`list_campaigns`	List email marketing campaigns with their status, audience size, and headline metrics.
`get_campaign`	Get full details for one campaign: content, audience segment, schedule, and delivery statistics (sent, opened, clicked, bounced, complained)..
`create_campaign`	Create a new email marketing campaign as a draft.
`send_campaign`	Send a campaign now, or schedule it for a future time by passing scheduled_at.
`list_contacts`	List contacts with their subscription status and engagement metrics.
`create_contact`	Add a single contact.
`update_contact`	Update an existing contact by email address, including changing subscription status.
`import_contacts`	Bulk-import up to 5,000 contacts in one call.
`get_contact_score`	Get engagement score, engagement tier, and churn risk for one contact — or the lowest-engagement contacts across the list when contact_id is omitted.
`list_templates`	List saved email templates with their variable placeholders, so you can pick one for a campaign or transactional send..
`create_template`	Create a reusable email template.
`render_template`	Render a template with sample variables and return the resulting HTML and subject.
`list_automations`	List automation workflows (welcome series, re-engagement, drip sequences) with their trigger type and active state..
`get_automation`	Get one automation workflow in full: trigger, every step with its delay, and per-step completion stats..
`create_automation`	Create an automation workflow from a trigger, saved as a paused draft.
`toggle_automation`	Activate or pause an automation.
`list_ab_tests`	List A/B tests with per-variant results and whether a winner has been selected yet..
`create_ab_test`	Create one A/B test variant on a campaign.
`select_ab_test_winner`	Select the winning variant and send it to the remaining audience.
`get_analytics`	Get delivery and engagement analytics — sent, delivered, opened, clicked, bounced, and complained — for the account or one campaign, grouped by day/week/month..
`get_analytics_timeline`	Get a day/week/month breakdown of sent, delivered, opened, clicked, bounced, complained, replied, and unsubscribed — across every send medium (campaigns, inbox compose, API, MCP, SDKs, GraphQL, automations).
`generate_report`	Generate a structured analytics report over a date range.
`get_revenue_attribution`	Attribute ecommerce revenue to email — revenue per campaign, per contact, and average order value from tracked conversions..
`get_monetization_stats`	Get newsletter monetization stats: paid subscribers, MRR, churn, and sponsorship revenue for the period..
`get_deliverability_score`	Get the account deliverability score (0–100) and letter grade (A–F) with the factors dragging it down.
`run_deliverability_audit`	Run a full deliverability audit across authentication (SPF/DKIM/DMARC), domain reputation, list hygiene, content signals, and blocklist status.
`get_warmup_status`	Get IP/domain warm-up progress and today's remaining send capacity.
`check_dmarc`	Check live SPF, DKIM, and DMARC DNS records for a domain and report alignment problems with the exact record to publish.
`list_domains`	List sending domains with verification status and their DKIM/SPF/DMARC records.
`add_domain`	Add a sending domain and return the DNS records to publish.
`verify_domain`	Re-check a domain's DNS records and mark it verified if they resolve.
`configure_inbound_domain`	Configure inbound email routing for a subdomain so replies land in the MisarMail unified inbox.
`list_forms`	List signup forms with their embed status and conversion counts..
`get_form`	Get one signup form including its fields, embed code, and redirect behaviour..
`get_form_submissions`	List submissions for a signup form, including the submitted field values and timestamps..
`create_landing_page`	Create a hosted landing page with a single hero block (headline, subheadline, CTA).
`list_marketplace_items`	Browse the MisarMail template marketplace for ready-made email and automation templates..
`get_marketplace_item`	Get one marketplace listing with its full preview, author, and install count..
`list_inbox_conversations`	List unified-inbox conversations (threads) with their status and detected intent.
`get_inbox_conversation_messages`	Get every message in one inbox conversation, oldest first, with sender and timestamps..
`categorize_inbox_emails`	Run AI categorisation over a batch of inbox emails to label intent and priority.
`list_api_keys`	List API keys on the account with their scopes and last-used time.
`generate_subject_lines`	Generate AI subject-line variants for a campaign topic, optionally tuned to a tone and audience.
`list_integrations`	List connected third-party integrations and their sync status..
`get_integration`	Get one integration's configuration, scopes, and last sync result..
`toggle_integration`	Enable or disable an integration.
`list_sandbox_sends`	List emails captured by sandbox mode.
`clear_sandbox`	Delete every captured sandbox email.
`upgrade`	Show the current MisarMail plan, how much of each quota is left, and what upgrading unlocks.

Prompts

Reusable workflows your client exposes as slash-commands.

Prompt	Description
`compose_email`	Draft a professional email and send it via MisarMail after confirmation.
`campaign_performance_report`	Analyse campaign performance and produce prioritized improvements.
`contact_import_guide`	Import and organise contacts safely, with consent and hygiene checks.
`automation_builder_guide`	Design and build an email automation workflow step by step.
`deliverability_improvement_plan`	Diagnose deliverability and produce a prioritized weekly action plan.
`ab_test_plan`	Design a statistically meaningful A/B test for a campaign.
`list_hygiene_audit`	Find and clean the contacts that are hurting sender reputation.
`weekly_email_report`	Produce a stakeholder-ready weekly email performance summary.

Resources

Read-only context an agent can attach without spending a tool call.

URI	Description
`misarmail://account/domains`	Your sending domains with verification state and DNS records.
`misarmail://account/deliverability`	Current account deliverability score (0–100), grade, and contributing factors..
`misarmail://account/warmup`	IP/domain warm-up stage and remaining send capacity for today — the ceiling a bulk send must stay under..
`misarmail://templates`	Saved templates with their declared variables, for reuse in campaigns and sends..

Agent skills

Bundled in skills/ — guidance an agent loads when a task matches.

Skill	Use when
`ab-test-campaign`	Design and run an A/B test on a MisarMail campaign — subject line, content, sender name, or send time. Use for "A/B test", "split test", "which subject works better", or testing email variants.
`audit-deliverability`	Diagnose why MisarMail emails land in spam or bounce, and produce a prioritized fix list. Use for "emails going to spam", "not being delivered", "low open rate", "domain reputation", DMARC/SPF/DKIM, or blocklist questions.
`build-email-automation`	Design and build a MisarMail automation workflow — welcome series, drip sequence, re-engagement, or onboarding. Use for "automate", "drip", "welcome series", "sequence", or trigger-based email.
`clean-contact-list`	Audit and clean a MisarMail contact list — bounced, complained, and unengaged contacts. Use for list hygiene, re-engagement, suppression, or "why is my open rate falling".
`email-performance-report`	Produce a MisarMail performance report — opens, clicks, deliverability, revenue attribution. Use for "how are my emails doing", weekly/monthly reports, or campaign performance analysis.
`run-email-campaign`	Create, review, and send a bulk email campaign in MisarMail. Use when the user wants to email a list, newsletter, segment, or announcement to many recipients.
`send-transactional-email`	Send a one-off or transactional email through MisarMail. Use when the user asks to send, draft-and-send, or reply to an email — including receipts, notifications, welcome messages, and personal outreach.
`setup-sending-domain`	Add and verify a custom sending domain in MisarMail, including SPF, DKIM, DMARC, and inbound routing. Use for "send from my own domain", DNS setup, domain verification, or inbound email.

Safety

Destructive and irreversible actions are annotated (destructiveHint) so clients can prompt before running them. The skills instruct agents to confirm before anything that sends mail, publishes content, or is otherwise visible to other people.

Discovery (initialize, tools/list, prompts/list, resources/list) never requires credentials, so registries can index the server without one. Every action does.

Install

Tools (54)

send_emaillist_emailsget_emailreply_to_emailarchive_emailvalidate_emaillist_campaignsget_campaign

Configuration

Environment variables

MISARMAIL_API_KEYsecret

Your MisarMail API key (msk_…). Create one at https://mail.misar.io/developers, or omit it and run the "login" tool to authenticate via browser.

MISARMAIL_BASE_URL

Override the API base URL. Only needed for self-hosted instances.

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "misarmail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@misarmail/mcp@5.1.2"
      ],
      "env": {
        "MISARMAIL_API_KEY": "<YOUR_MISARMAIL_API_KEY>",
        "MISARMAIL_BASE_URL": "<YOUR_MISARMAIL_BASE_URL>"
      }
    }
  }
}

MisarMail MCP Server (io.github.Misar-AI/misarmail-mcp)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

send_email

list_emails

get_email

reply_to_email

archive_email

validate_email

list_campaigns

get_campaign

create_campaign

send_campaign

list_contacts

create_contact

update_contact

import_contacts

get_contact_score

list_templates

create_template

render_template

list_automations

get_automation

create_automation

toggle_automation

list_ab_tests

create_ab_test

select_ab_test_winner

get_analytics

generate_report

get_revenue_attribution

get_monetization_stats

get_deliverability_score

run_deliverability_audit

get_warmup_status

check_dmarc

list_domains

add_domain

verify_domain

configure_inbound_domain

list_forms

get_form

get_form_submissions

create_landing_page

list_marketplace_items

get_marketplace_item

list_inbox_conversations

get_inbox_conversation_messages

categorize_inbox_emails

list_api_keys

generate_subject_lines

list_integrations

get_integration

toggle_integration

list_sandbox_sends

clear_sandbox

upgrade

MisarMail MCP Server

Install

Smithery (recommended)

Claude Code

Manual (any client)

Remote (no install)

Authentication

Tools

Prompts

Resources

Agent skills

Safety

Links

Install

Configuration

Related servers