# MisarMail Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## MisarMail

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

- Record: https://musedirectory.ai/connector/misarmail
- Category: Marketing & Ads
- Developer: Misar AI (https://www.misarmail.com)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 712ms, checked 2026-09-28T10:00:55Z
- Endpoint: https://api.misar.io/mail/mcp
- Auth: Needs an access key; Pricing: unknown
- Screening: Screened, no issues found (2026-09-25T03:16:13Z)
- Source: Found in the official MCP Registry (io.github.Misar-AI/misarmail-mcp) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.Misar-AI%2Fmisarmail-mcp

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.

Example request: "Send a welcome email to new customers and enroll them in a drip campaign."

How to connect: Not 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.

Tools:
- 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.
- 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.
- 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.
- 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.
- 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 rea
- 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.
- 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.
- 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. Creating never sends — call send_campaign separately once the content and audience are confirmed.
- 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.
- 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.
- 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.
- update_contact: Update an existing contact by email address, including changing subscription status. Setting status to unsubscribed immediately excludes them from every future campaign.
- 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.
- 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.
- 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 a
- create_template: Create a reusable email template. Use {{variable}} placeholders for personalisation — they are substituted at send time and previewable via render_template.
- render_template: Render a template with sample variables and return the resulting HTML and subject. Use this to preview personalisation before sending anything.
- 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
- 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 o
- 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.
- 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_autom
- 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, irre
- 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.
- 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.
- 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.
- 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).
- 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 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- configure_inbound_domain: Configure inbound email routing for a subdomain so replies land in the MisarMail unified inbox. Returns the MX record to publish.
- 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 
- 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_subm
- 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 sh

Screening checks:
- MCP handshake: pass (Answered in 958ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api.misar.io, www.misarmail.com not flagged)
- Published packages against the OSV malicious-package database: pass (No malicious-package advisories)
- Hidden instructions or invisible characters in tool text: pass (54 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)