MisarMail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL of the MisarMail MCP server, typically https://mail.misar.io/api/mcp | |
| transport | Yes | The transport protocol used to communicate with the server (e.g., 'http') |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailA | Send a transactional email from a verified MisarMail account. |
| list_emailsA | 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_emailA | 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_emailA | 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_emailA | Move an email to the archive folder. Reversible — the message is not deleted. |
| validate_emailA | 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_campaignsA | 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_campaignA | Get full details for one campaign: content, audience segment, schedule, and delivery statistics (sent, opened, clicked, bounced, complained). |
| create_campaignA | Create a new email marketing campaign as a draft. Creating never sends or schedules anything — once the content and audience are confirmed, call send_campaign to send it now or schedule it for later. |
| send_campaignA | 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_contactsA | 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_contactA | 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_contactA | Update an existing contact by email address, including changing subscription status. Setting status to unsubscribed immediately excludes them from every future campaign. Does not support tags, phone, company, or job title — the API has no fields for them. |
| import_contactsA | Bulk-import up to 5,000 contacts in one call. By default, addresses that already exist are skipped rather than duplicated — pass update_existing: true to update them instead. Returns per-row results so you can see which rows were rejected and why. |
| get_contact_scoreA | 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_templatesA | List saved email templates with their variable placeholders, so you can pick one for a campaign or transactional send. |
| create_templateA | Create a reusable email template. Use {{variable}} placeholders for personalisation — they are substituted at send time and previewable via render_template. |
| render_templateA | Render a template with sample variables and return the resulting HTML and subject. Use this to preview personalisation before sending anything. |
| list_automationsB | List automation workflows (welcome series, re-engagement, drip sequences) with their trigger type and active state. |
| get_automationA | Get one automation workflow in full: trigger, every step with its delay, and per-step completion stats. |
| create_automationA | Create an automation workflow from a trigger, saved as a paused draft. The API's create endpoint only accepts a name and trigger — it has no fields for workflow steps or starting active; configure the step sequence in the MisarMail dashboard's visual builder, and use toggle_automation to activate once reviewed. |
| toggle_automationA | Activate or pause an automation. Activating starts enrolling contacts and sending on the configured schedule. |
| list_ab_testsB | List A/B tests with per-variant results and whether a winner has been selected yet. |
| create_ab_testA | Create one A/B test variant on a campaign. The real API stores a single variant per call, so build a test by calling this once per variant (e.g. twice for a plain A/B split) using the same campaign_id and distinct |
| select_ab_test_winnerA | 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_analyticsA | 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_timelineA | 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). The timeline counterpart to get_analytics's period totals. |
| generate_reportB | 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_attributionB | Attribute ecommerce revenue to email — revenue per campaign, per contact, and average order value from tracked conversions. |
| get_monetization_statsA | Get newsletter monetization stats: paid subscribers, MRR, churn, and sponsorship revenue for the period. |
| get_deliverability_scoreA | 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_auditA | Run a full deliverability audit across authentication (SPF/DKIM/DMARC), domain reputation, list hygiene, content signals, and blocklist status. Returns prioritized findings. |
| get_warmup_statusA | 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_dmarcA | 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_domainsA | 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_domainA | 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_domainA | 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_domainA | Configure inbound email routing for a subdomain so replies land in the MisarMail unified inbox. Returns the MX record to publish. |
| list_formsA | List signup forms with their embed status and conversion counts. |
| get_formA | Get one signup form including its fields, embed code, and redirect behaviour. |
| get_form_submissionsA | List submissions for a signup form, including the submitted field values and timestamps. |
| create_landing_pageA | Create a hosted landing page with a single hero block (headline, subheadline, CTA). Returns the public URL. The real API stores pages as a page-builder block array with no dedicated headline/CTA fields, so this tool translates your inputs into one 'hero' block — for multi-block pages or a real CTA link, use the landing page editor in the MisarMail dashboard. |
| list_marketplace_itemsA | Browse the MisarMail template marketplace for ready-made email and automation templates. |
| get_marketplace_itemA | Get one marketplace listing with its full preview, author, and install count. |
| list_inbox_conversationsA | List unified-inbox conversations (threads) with their status and detected intent. Use this for triage; use list_emails for individual messages in a folder. |
| get_inbox_conversation_messagesA | Get every message in one inbox conversation, oldest first, with sender and timestamps. |
| categorize_inbox_emailsA | 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. |
| list_api_keysA | List API keys on the account with their scopes and last-used time. Key secrets are never returned — only metadata. |
| generate_subject_linesA | Generate AI subject-line variants for a campaign topic, optionally tuned to a tone and audience. Good input for create_ab_test. |
| list_integrationsA | List connected third-party integrations and their sync status. |
| get_integrationA | Get one integration's configuration, scopes, and last sync result. |
| toggle_integrationA | Enable or disable an integration. Disabling stops all syncing but preserves the stored credentials. |
| list_sandbox_sendsA | List emails captured by sandbox mode. Sandbox intercepts sends instead of delivering them — use it to verify templates and automations without emailing anyone. |
| clear_sandboxA | Delete every captured sandbox email. Affects only intercepted test messages, never real sent mail. |
| upgradeA | Show the current MisarMail plan, how much of each quota is left, and what upgrading unlocks, with the link to upgrade. Call it any time — not only after hitting a limit. Reads only: it never changes the plan or takes payment; the user upgrades by following the link. On a local install, open=true also opens that link in the user's browser. |
| loginA | Authenticate with your MisarMail account via browser — no API key copy-paste needed. Opens the MisarMail authorization page where you review the requested permissions and click 'Authorize'. The API key is delivered straight back to this client and saved to ~/.misarmail/config.json. |
| logoutA | Forget the locally stored MisarMail API key (~/.misarmail/config.json). Does not revoke the key server-side — delete it from mail.misar.io/developers to do that. |
| auth_statusA | Check whether this client is authenticated, which MisarMail account the stored key belongs to, and which API base URL it targets. Run this first when a tool reports an auth error. |
Prompts
Interactive templates invoked by user choice
| Name | 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
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Verified sending domains | Your sending domains with verification state and DNS records. Read this before composing any send — an unverified sender is the most common send failure. |
| Deliverability score | Current account deliverability score (0–100), grade, and contributing factors. |
| Warm-up capacity | IP/domain warm-up stage and remaining send capacity for today — the ceiling a bulk send must stay under. |
| Email templates | Saved templates with their declared variables, for reuse in campaigns and sends. |
TDQS
Scored across 58 tools
Most tools have distinct resource+action targets, and descriptions cross-reference siblings (e.g., list_inbox_conversations vs list_emails). However, with 58 tools there are clusters that can confuse: list_emails/get_email/get_inbox_conversation_messages, get_analytics/get_analytics_timeline/generate_report, and get_deliverability_score/run_deliverability_audit/check_dmarc. Descriptions mitigate but not eliminate overlap.
Predominantly snake_case verb_noun (list_campaigns, create_campaign, send_campaign), which is predictable. Exceptions like login, logout, upgrade, auth_status, and check_dmarc are minor deviations; overall still readable and consistent.
58 tools is far above the typical 3-15 range and exceeds the 25+ 'heavy' threshold by a wide margin. While each maps to a subdomain, the volume increases discovery and misselection risk for agents; consolidation would help.
Core workflows are covered (campaigns, contacts, templates, domains, inbox, automations, analytics), but several resources lack full lifecycle: no update/delete for campaigns/templates/contacts, no automation step editing, no form creation, and landing pages only have create. These are notable gaps, though many can be worked around via the dashboard.