Skip to main content
Glama

Related Servers

Alternatives to MisarMail MCP Server

  • A
    license
    B
    quality
    C
    maintenance
    Enables management of AI-powered email marketing automation, including subscriber segments, campaigns, and templates. It allows users to generate email sequences with AI and track detailed analytics through natural language commands.
    100
    1,311 npm
    2
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    AI-native email marketing platform built for agents. Control campaigns, automations, contacts, templates, and analytics via MCP with OAuth authentication.
    33 npm
    2
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    An MCP server providing comprehensive email capabilities via IMAP and SMTP, enabling AI assistants to read, search, send, manage, schedule, and analyze emails across multiple accounts.
    49
    1,108 npm
    117
    LGPL 3.0

Related Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    Provides 35 MCP tools for automated marketing campaigns, integrating event management, booking, and email marketing into a deterministic pipeline for AI agents.
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI assistants to read, search, send, manage, schedule, and analyze emails across multiple IMAP/SMTP accounts via MCP, with features like OAuth2, calendar extraction, analytics, and real-time email watching.
    LGPL 3.0
  • A
    license
    A
    quality
    C
    maintenance
    Email-deliverability tools for AI agents — 12 MCP tools across email verification, DNSBL across 50 zones, SPF/DKIM/DMARC analysis, spam-trap scoring, domain intelligence, and email finder. Free tier with no credit card.
    12
    44 npm
    1
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    An MCP server for the PostStack email API that enables AI assistants to send transactional emails, manage contacts, handle inbound email threads, and perform deliverability checks through 84 curated tools.
    84
    237 npm
    1
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    MCP server for SentVia that provides email infrastructure for AI agents, enabling them to create inboxes, send, reply, forward, search messages, manage drafts, domains, webhooks, and allow/block rules through 21 tools.
    21
    25 npm
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI assistants to manage email campaigns, contact lists, analytics, A/B tests, and transactional emails through natural language, using OAuth for secure connection.
    MIT

TDQS

A3.9/5.0

Scored across 57 tools

Disambiguation4/5

Most tools have clearly distinct purposes (send vs list vs create vs analytics), and the descriptions carefully disambiguate overlapping areas like list_emails vs list_inbox_conversations and list_templates vs list_marketplace_items. A few pairs like get_analytics vs generate_report and get_deliverability_score vs run_deliverability_audit could still be confused at a glance, but the descriptions resolve the boundary.

Naming Consistency4/5

The set overwhelmingly follows a consistent verb_noun pattern: list_*, get_*, create_*, send_*, update_*, toggle_*, verify_*, check_*. Minor deviations exist (login/logout/auth_status, upgrade, clear_sandbox, render_template) but they are conventional and do not break the overall pattern.

Tool Count3/5

57 tools is a large surface for one server, and while the domain is broad (email sending, campaigns, contacts, forms, landing pages, automations, A/B testing, analytics, deliverability, integrations, sandbox, auth), the count pushes into the heavy range. Each tool appears to earn its place, but an agent will face a long list to choose from.

Completeness4/5

The server covers the email marketing lifecycle well: sending, receiving, contacts, campaigns, templates, automations, A/B tests, analytics, deliverability, and integrations. Minor gaps exist — e.g., no update_campaign, no delete_campaign, no delete_contact, no update_template — but the core workflows are complete and the gaps are workable.

Maintenance

ActivityMaintained
ResponsivenessNo issues