Skip to main content
Glama
gfam-git

Simple IMAP MCP Server

by gfam-git
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Simple IMAP MCP Server

No user-submitted related servers found.

    Related Servers

    • Gmail MCP Server

      franciscpd
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading, searching, sending, replying, forwarding emails, and managing labels in Gmail through the Model Context Protocol.
      27 npm
      3
      MIT

    • MCP

      Leev1s
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables reading and drafting emails via IMAP, including searching and managing drafts, through natural language.
      1,026 npm
      MIT

    • Proton Mail MCP Server

      fincher65
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to send, read, search, and organize Proton Mail email via SMTP and IMAP through the Model Context Protocol.
      MIT
    • @sendraven/mcp by CommonNinja

      @sendraven/mcpofficial

      CommonNinja
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to send and manage email, read threaded replies, run campaigns and automations, and handle approvals through the Model Context Protocol from any compatible client.
      45
      747 npm
      1
      MIT

    • Email MCP Server

      gabigabogabu
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables email integration via IMAP and SMTP, allowing model assistants to read, send, search emails, and list folders.
      21 npm
      14
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 16 tools

    Disambiguation4/5

    Each tool targets a distinct operation—full fetch, body-only, headers-only, flags, folder ops, drafts—but send_email and send_email_with_attachment, plus the three retrieval variants, have close functional boundaries that require careful description reading.

    Naming Consistency3/5

    Most names follow snake_case verb_noun, but verbs are inconsistent (fetch vs get vs list), list_unread omits the object, and email_waiting reverses the expected verb-object order.

    Tool Count4/5

    Sixteen tools is on the high end but each maps to a real email workflow—retrieve, search, send, draft, folder management—so the count is only slightly above the ideal range.

    Completeness4/5

    The surface covers retrieval, search, read state, move/delete, folder listing/creation, sending with and without attachments, and draft CRUD. Missing folder deletion/rename and attachment-only retrieval are minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources