Send transactional and marketing email, manage contacts, run campaigns and automations, track deliverability.
Connect to MisarMail to send transactional emails, create and launch marketing campaigns, manage contact lists and automations, validate email addresses, run A/B tests, and audit email deliverability. Track opens, clicks, bounces and revenue attribution.
Try asking Muse: "Send a welcome email to new customers and enroll them in a drip campaign."
Source: Found in the official MCP Registry (io.github.Misar-AI/misarmail-mcp) · First listed September 25, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
What Muse can see: You sign in to your own account with it, so Muse can reach what that account allows. Read what it asks for before you agree.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://api.misar.io/mail/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Response time at the last check: 1340ms. Worked in 100% of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
send_emailSend 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.list_emailsList 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.get_emailRead the full content of a single email by ID, including headers, body, and attachments metadata. Side effect: marks the email as read.reply_to_emailReply to an existing email thread. The sender address and threading headers are derived from the original message, so only the body is required.archive_emailMove 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 reavalidate_emailValidate an email address before sending: syntax, MX records, disposable-domain and role-account detection. Use this to protect sender reputation on imported lists.list_campaignsList email marketing campaigns with their status, audience size, and headline metrics. Filter by status to find drafts ready to send or campaigns still sending.get_campaignGet full details for one campaign: content, audience segment, schedule, and delivery statistics (sent, opened, clicked, bounced, complained).create_campaignCreate a new email marketing campaign as a draft. Creating never sends — call send_campaign separately once the content and audience are confirmed.send_campaignSend 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.list_contactsList contacts with their subscription status and engagement metrics. Filter by status to find unsubscribed or bounced addresses that should be excluded from sends.create_contactAdd 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.update_contactUpdate an existing contact by email address, including changing subscription status. Setting status to unsubscribed immediately excludes them from every future campaign.import_contactsBulk-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.get_contact_scoreGet 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.list_templatesList 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 acreate_templateCreate a reusable email template. Use {{variable}} placeholders for personalisation — they are substituted at send time and previewable via render_template.render_templateRender a template with sample variables and return the resulting HTML and subject. Use this to preview personalisation before sending anything.list_automationsList 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_automationget_automationGet 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 ocreate_automationCreate 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.toggle_automationActivate 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_automlist_ab_testsList 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, irrecreate_ab_testCreate 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.select_ab_test_winnerSelect 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.get_analyticsGet delivery and engagement analytics — sent, delivered, opened, clicked, bounced, and complained — for the account or one campaign, grouped by day/week/month.generate_reportGenerate 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).get_revenue_attributionAttribute ecommerce revenue to email — revenue per campaign, per contact, and average order value from tracked conversions.get_monetization_statsGet 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_revenueget_deliverability_scoreGet 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_auditRun a full deliverability audit across authentication (SPF/DKIM/DMARC), domain reputation, list hygiene, content signals, and blocklist status. Returns prioritized findings.get_warmup_statusGet 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.check_dmarcCheck 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.list_domainsList sending domains with verification status and their DKIM/SPF/DMARC records. Check here first when a send fails with an unverified-sender error.add_domainAdd a sending domain and return the DNS records to publish. The domain cannot send until those records are live and verify_domain succeeds.verify_domainRe-check a domain's DNS records and mark it verified if they resolve. Safe to retry — DNS propagation can take up to 48 hours.configure_inbound_domainConfigure inbound email routing for a subdomain so replies land in the MisarMail unified inbox. Returns the MX record to publish.list_formsList 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 get_formGet 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_submget_form_submissionsList 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 shhttps://api.misar.io/mail/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use MisarMail to help me. It is a free service with an MCP server at https://api.misar.io/mail/mcp. It needs an API key from Misar AI; ask me to enter it through your secure credential prompt. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (September 28, 2026, 07:31 UTC) the endpoint was working, answering in 1340ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
It was screened on September 25, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 40 tools, including send_email, list_emails, get_email, reply_to_email. For example, you could ask Muse: "Send a welcome email to new customers and enroll them in a drip campaign."
This listing was added from public sources (Found in the official MCP Registry (io.github.Misar-AI/misarmail-mcp)). If you build MisarMail, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/misarmail"><img src="https://musedirectory.ai/badge/misarmail.svg" alt="MisarMail on musedirectory.ai" width="236" height="40"></a>