Skip to main content
Glama
salahawad

outlook-personal-mcp

by salahawad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to outlook-personal-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      8 npm
      MIT

    • outlook-mcp

      8C9D
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that connects Claude to a personal Microsoft Outlook mailbox via Microsoft Graph, providing tools for mail, calendar, contacts, tasks, and settings with a strong security model.
      144 npm
      MIT

    • hotmail-mcp

      oshann
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that connects Claude Desktop to a personal Hotmail/Outlook.com mailbox via Microsoft Graph API, enabling email management, rule handling, and composing messages.
      25
      MIT

    • outlook-mcp

      hamzashahbaz
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables Claude to manage Outlook emails, including reading, sending, organizing, drafting, and bulk operations via Microsoft Graph API.
      15 npm
      1
      MIT

    • Outlook MCP Python

      cycle-sync-ai
      F
      license
      Not graded
      quality
      D
      maintenance
      A Python-based MCP server for Microsoft Outlook integration using Microsoft Graph API, enabling email reading/sending, calendar management, and contact operations through Claude Desktop.
      1
      -
    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.6/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: folder operations are separate from message operations, and draft/attachment/calendar tools are clearly partitioned. Even overlapping tools like list_messages vs search_messages are differentiated by filtering vs full-text search. No two tools appear to do the same thing.

    Naming Consistency5/5

    The vast majority follow a consistent verb_noun pattern (delete_folder, send_mail, create_event). Minor deviations like whoami and short verbs reply/forward are still intuitive and do not disrupt the overall predictable scheme.

    Tool Count4/5

    At 31 tools, this is a relatively large surface, but the server covers two major domains (mail and calendar) with comprehensive operations. Each tool maps to a meaningful operation, so while the count is above the typical 3-15 range, it is justified by the scope and does not feel padded.

    Completeness5/5

    The tool set provides full lifecycle coverage for folders, messages, drafts, and calendar events: create, read, update, delete, search, and specialized actions (reply, forward, respond, find_availability). There are no obvious dead ends; every workflow from composing a draft to sending it, or from listing events to updating them, is supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources