MisarMail MCP Server

by misar-mail Your server? Claim it

answering

MisarMail is answering right now. Last checked 12 min ago. It exposes 54 tools.

Full email marketing platform: inbox, campaigns, contacts, templates, and analytics via MCP.

Uptime history 51 days of history · worst day 45%

51 days agonow

98.9%

Uptime 24h

90 of 91 checks

Tools

read from the server

801 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 18

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 August 2026. No other catalogue keeps this.

19 Aug 18 tool descriptions were rewritten archive_email, clear_sandbox, get_automation and 15 more

MisarMail does not always answer

Over the last week it answered 97.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add misarmail --transport http https://mail.misar.io/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "misarmail": {
      "url": "https://mail.misar.io/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.misarmail]
url = "https://mail.misar.io/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "misarmail": {
      "url": "https://mail.misar.io/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "misarmail": {
      "url": "https://mail.misar.io/api/mcp"
    }
  }
}

Available tools 54

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

contact

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.

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.

update_contact

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

automation

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.

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.

campaign

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.

get_campaign

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

deliverability

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.

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.

form

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.

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.

generate

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).

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.

inbox

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.

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.

marketplace

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.

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.

send

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.

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.

toggle

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.

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.

analytics

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.

api

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.

archive

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.

automations

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.

campaigns

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.

categorize

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.

clear

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.

configure

configure_inbound_domain

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

contacts

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.

dmarc

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.

domain

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.

domains

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.

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.

emails

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.

forms

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.

import

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.

integration

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.

integrations

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.

landing

create_landing_page

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

monetization

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.

render

render_template

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

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.

revenue

get_revenue_attribution

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

sandbox

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.

select

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.

template

create_template

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

templates

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.

test

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.

tests

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.

upgrade

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.

validate

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.

verify

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.

warmup

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mail.misar.io/api/mcp	streamable-http	answering	653 ms	12 min ago

Alternatives to MisarMail

same job, measured the same way

Mailercloud Com

by mailercloud-com

AI tools for Mailercloud email marketing: campaigns, contacts, templates, sending & analytics.

answering

MCP Mailtrap

by pijusz

MCP server for the Mailtrap email platform — analytics, sending, contacts, sandbox

27 installs/wk local only

Nitrosend

by nitrosend

AI-native email marketing. Campaigns, automations, transactional, contacts, and analytics.

46 installs/wk local only

SendGrid MCP Server

by deyikong

MCP server for SendGrid's v3 API: email marketing, transactional mail, templates, and analytics.

221 installs/wk local only

Sendgrid

by usefulapi

Send email and read templates, marketing contacts, lists, stats, bounces and unsubscribes.

11 tools answering

RuSender

by rusender

Manage email campaigns, contacts and deliverability analytics in RuSender from an AI assistant.

answering

Scribe

by scribe-mail

Manage Scribe email signatures: templates, teammates, smart fields and campaigns, via OAuth.

answering

PulsyAI

by pulseem

Send SMS, WhatsApp & email, manage contacts and campaigns, and pull reports via Pulseem.

3 tools answering

MisarMail — questions

Answers built from our own checks of this server.

What can MisarMail do?

It exposes 54 tools, read directly from the server on our last check. Among them: add_domain, archive_email, categorize_inbox_emails, check_dmarc, clear_sandbox, configure_inbound_domain and 48 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is MisarMail mostly used for?

Its tools cluster around contact, campaign and deliverability. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is MisarMail working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 801 ms. The bar chart above shows every period we have measured.

How do I connect MisarMail?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does MisarMail need an API key?

No. MisarMail completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 54 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is MisarMail?

It answers our handshake in 801 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.