Skip to main content
Glama
mailroom-mcp

mailroom-mcp

by TayebKahia

Related Servers

Alternatives to mailroom-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to read and organize mail, manage drafts, and perform broader mailbox operations under configurable read-only, draft-only, or full-access modes.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read, search, organize, draft, and send email across connected mailboxes with configurable access levels and auditable, undoable actions.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables software agents to read and manage their own mailboxes, inspect inbound messages, and request outbound email that remains pending until an owner approves it. Exposes these agent mail operations as remote MCP tools alongside a REST API.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI assistants to securely search multiple mailboxes, reconstruct email threads, and inspect attachments through read-only tools without altering mailbox state.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to search and read an IMAP mailbox, extract attachment text, reconstruct threads, and prepare plain-text drafts for review and manual sending, without sending, moving, deleting, modifying, or marking messages as read.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to manage multiple IMAP/SMTP mailboxes by listing folders, searching and reading messages, preparing Markdown drafts and replies, and sending only a draft the user has reviewed and confirmed.
      9
      44 npm
      MIT

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct read target: conversation lists, a single conversation, pending approvals, audit trail, aggregate counts, KB questions, and redraft requests. There is mild overlap between list_conversations (filterable by status), list_pending_approvals, and inbox_summary, but the descriptions clearly separate list vs. queue vs. aggregate views.

    Naming Consistency4/5

    Six of seven tools follow a consistent verb_noun pattern (list_conversations, get_conversation, list_pending_approvals, get_audit_trail, search_knowledge_base, request_redraft). inbox_summary breaks the pattern as a noun phrase, a minor but noticeable deviation.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and each maps to a distinct operator workflow step (triage, inspect, summarize, research, redraft). Nothing appears redundant or missing at the count level.

    Completeness4/5

    The surface covers listing, inspection, audit, summary, knowledge lookup, and redraft — a coherent read-and-request lifecycle with human approval intentionally excluded. Mutating operations like approve/reject/send are absent by design, so the only minor gap is the lack of a direct way to re-fetch or inspect a specific draft in isolation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues