Skip to main content
Glama
kalle-works

EuroMail MCP Server

by kalle-works

Related Servers

Alternatives to EuroMail MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to send and track transactional email, manage templates and sending domains, and read inbound email through the transactional email API.
      16
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to send transactional email, authenticate sending domains, track delivery, and diagnose deliverability issues programmatically.
      13
      301 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.
      28 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to send, receive, and track email and manage templates, domains, webhooks, and other email API operations from AI assistants.
      0
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to read, search, send, reply, forward, schedule, organize, and analyze email across multiple IMAP/SMTP accounts, with provider-aware labels, drafts, templates, and bulk operations. Additional capabilities include real-time IMAP IDLE watching with AI triage, verification-code capture, calendar extraction, analytics, and optional Streamable HTTP or OAuth2 access.
      20 npm
      ISC

    TDQS

    C2.9/5.0

    Scored across 56 tools

    Disambiguation4/5

    Most tools target a distinct resource+action pair, and the resource prefixes (email, template, domain, webhook, suppression, contact_list, inbound_route, mailbox) keep families cleanly separated. Minor overlap remains between send_email/send_batch_emails, get_email/get_inbound_email, and the four analytics tools, though descriptions differentiate them adequately.

    Naming Consistency4/5

    Nearly all names follow a snake_case verb_noun pattern with standard CRUD verbs (create_/get_/list_/update_/delete_). Deviations are the mixing of 'add_' (add_domain, add_suppression, add_contacts) and 'remove_' (remove_suppression, remove_contact) where create_/delete_ would be expected, but the convention is still predictable.

    Tool Count2/5

    56 tools is heavy even for a full transactional email platform, spanning email sending, templates, domains, webhooks, suppressions, contacts, analytics, dead letters, inbound, agent mailboxes, audit and billing. Each family is defensible, but the total surface is large enough to burden tool selection and context.

    Completeness4/5

    The surface covers the full lifecycle for most resources (templates, domains, webhooks, inbound routes, contact lists all have create/get/list/update/delete), plus sending, analytics, suppression and dead-letter recovery. Gaps exist around the agent mailbox resource (no get/update/delete mailbox) and contact-level updates, which agents must work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues