Skip to main content
Glama
LeeFlannery

imap-mcp

by LeeFlannery

Related Servers

Alternatives to imap-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for IMAP email access, enabling AI agents to read, search, and monitor email without sending or deleting messages.
      23 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that gives Claude unified access to multiple Gmail and Microsoft 365 accounts, enabling email search, reading, and listing through one connection.
      89 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A read-only Gmail MCP server enabling users to search and read emails via Gmail search syntax without sending, deleting, or modifying anything.
      89 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for Gmail that enables searching threads, reading messages, and listing labels without any write access.
      62 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A lightweight MCP server for interacting with IMAP email accounts to read messages, manage folders, and compose draft replies. It supports standard providers and local bridges, providing tools for searching, fetching attachments, and organizing mailboxes without the ability to send or delete emails.
      19
      8
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only IMAP server for the Model Context Protocol that lets users list mailboxes, search messages, and retrieve messages and attachments through MCP. It exposes Streamable HTTP at /mcp with strict safety limits.
      MIT

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing accounts, listing emails, searching emails, and fetching a single email. There is no overlapping purpose between them, and the parameters clearly differentiate list_emails from search_emails.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern: list_accounts, list_emails, search_emails, get_email. The naming is predictable and uniform.

    Tool Count5/5

    With 4 tools, the server is well-scoped for basic email retrieval. Each tool earns its place, covering the essential actions without unnecessary bloat or redundancy.

    Completeness4/5

    The set covers the core email-reading workflow: identify accounts, list/search emails, and fetch full content. Minor gaps like flag management or folder operations exist, but the primary use case is fully supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues