Skip to main content
Glama
jahfer

JMAP MCP Server

by jahfer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to JMAP MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-hey

      Sealjay
      A
      license
      A
      quality
      A
      maintenance
      Local MCP server for Hey.com email - read, search, send, reply, and manage the screener via stored session cookies. Runs over stdio, stores no credentials.
      37
      12
      MIT

    • mcp-gmail-oauth

      flujo-app
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hostable Gmail MCP server that enables Gmail search/read, sending, replies, drafts, labels, and attachment downloads via MCP tools with OAuth authorization. Supports stdio and streamable HTTP transports.
      1
      MIT

    • mcp-email

      algonacci
      A
      license
      Not graded
      quality
      C
      maintenance
      A minimal MCP server for reading, searching, managing, and sending email over IMAP and SMTP.
      MIT

    • email-mcp

      swapnilsurdi
      A
      license
      A
      quality
      D
      maintenance
      Local MCP server for multi-account IMAP/SMTP email (iCloud + Gmail via app-specific passwords). Never marks mail read. Cross-folder search, idempotent sends, TLS verified.
      8
      MIT
    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

    D1.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: get_email_content retrieves specific email content, get_mailboxes lists mailboxes, and search_emails searches across emails. There is no overlap in functionality, making it easy for an agent to select the right tool for each task.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (get_email_content, get_mailboxes, search_emails). The naming is predictable and readable throughout the set.

    Tool Count3/5

    With only 3 tools, the set feels thin for an email server, as it lacks operations like creating, updating, or deleting emails or mailboxes. While the tools cover basic retrieval and search, the scope is limited and may not support full email workflows.

    Completeness2/5

    The tool surface is significantly incomplete for an email domain, missing essential CRUD operations such as send_email, delete_email, create_mailbox, or update_email. This will likely cause agent failures when attempting comprehensive email management tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources