Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Related Servers

Alternatives to langmail-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI assistant to access and manage mail, calendar, contacts, files, sharing, and Sieve through a local Stalwart JMAP server, with configurable write policies that require confirmation for irreversible actions.
      28 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI agents to self-hosted Stalwart mail servers via a Cloudflare Worker and JMAP, enabling mailbox search, reading, listing, and two-step draft-and-send email operations through MCP.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage email over JMAP, including inspecting mailboxes, searching and retrieving messages, navigating threads, downloading attachments, triaging inboxes, and sending emails atomically via HTTP.
      42 PyPI
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to manage mailbox contents and schedules through IMAP/SMTP/CalDAV, including searching, reading, sending emails with signatures and attachments, and creating or responding to calendar events.
      19
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with email accounts via IMAP and SMTP, supporting mailbox listing, email search, retrieval, sending, and management.
      MIT

    TDQS

    A4.1/5.0

    Scored across 40 tools

    Disambiguation4/5

    The set is mostly well partitioned by resource and action: mail reading, mail state changes, drafts, rules, calendars, events, and contacts each have clear boundaries. The main overlaps are between staging and immediate-send tools (create_draft vs reply_to_message/forward_message) and between preview/get email, though descriptions explicitly clarify when to use each.

    Naming Consistency5/5

    Tool names consistently use snake_case with a verb-resource structure: get_email, search_emails, create_calendar_event, update_mail_rule, delete_contact, etc. Minor variants such as unsubscribe_from_list and list_upcoming_birthdays are still readable and fit the overall convention.

    Tool Count2/5

    Although the server spans several domains (mail, drafts, rules, calendar, contacts), 40 tools is heavy and exceeds the practical range for reliable selection. Some operations could be consolidated or expressed as parameters rather than separate tools, especially around sending vs drafting and preview vs validation.

    Completeness4/5

    Coverage is broad: email search/read/state changes, draft lifecycle, mail-rule lifecycle, calendar/event CRUD plus RSVP, and contact CRUD/merge/birthdays are all present. A few gaps remain, most notably no delete_calendar operation and no explicit mailbox/folder creation or management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues