Skip to main content
Glama
injaan

@injaan.dev/ms365-email-cli-mcp

by injaan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @injaan.dev/ms365-email-cli-mcp

No user-submitted related servers found.

    Related Servers

    • outlook-mcp-server

      dhtim135
      F
      license
      A
      quality
      D
      maintenance
      A lightweight MCP server for personal Microsoft Outlook/Hotmail accounts, enabling email search, reading, attachment management, and folder operations via Microsoft Graph API with OAuth device-code flow.
      6
      1
      -

    • email-mcp

      contributory
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for reading, searching, sending, and managing emails via IMAP/SMTP, with tools like list_emails, read_email, search_emails, send_email, get_attachment, get_account_info, and mark_email_read.
      26 npm
      ISC

    • outlook-mcp-server

      acangialosi
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that gives Claude read/write access to a personal Hotmail/Outlook.com mailbox via the Microsoft Graph API, exposing tools for listing, searching, sending, and drafting emails.
      6
      7 npm
      MIT

    • zimbra-mcp

      dnlbertoni
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes a Zimbra mailbox (IMAP, SMTP, LDAP/GAL) as tools for AI assistants, enabling email search, retrieval, sending, attachment handling, and contact lookup via natural language.
      -
    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

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct email operation: listing, reading, threading, read status, searching, sending, replying, reply-all, and attachments. Even similar tools like list_emails and list_unread_emails are clearly separated by filter, so no real ambiguity.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (list_emails, read_email, mark_read, search_emails, send_email, reply_all), but 'thread' and 'attachment' are nouns, and 'reply' is a bare verb. The naming is readable but not perfectly uniform.

    Tool Count5/5

    With 10 tools, the server is well-scoped for an email CLI. Each tool addresses a core email workflow (read, list, search, send, reply, manage attachments), without excess or superficial additions.

    Completeness4/5

    The surface covers the main email lifecycle: list, read, search, send, reply, and attachments. Minor gaps exist such as no mark_unread, delete, or folder management, but these are not critical for basic email operations and can be worked around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources