Skip to main content
Glama
timfurlong

msgraph-mcp

by timfurlong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to msgraph-mcp

No user-submitted related servers found.

    Related Servers

    • exchange-ai-connector

      wteja
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to read and manage Microsoft 365/Outlook email and calendar, with destructive actions (send email, create event) requiring human approval.
      8
      MIT

    • outlook-mcp

      XenoXilus
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to manage Microsoft Outlook email and calendar through the Microsoft Graph API, including reading, sending, searching emails, and handling calendar events.
      43
      144 npm
      27
      MIT

    • m365-reporting-mcp

      kharonx
      F
      license
      B
      quality
      B
      maintenance
      Enables MCP-compatible AI clients to securely read a user's Microsoft 365 data across Outlook, Calendar, Teams, meetings, OneNote, SharePoint, OneDrive, Loop, and Search, and to send Outlook email only after explicit user confirmation.
      103
      -

    • @dockndevai/mcp-outlook

      dockndevai
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to read, search, draft, send, reply to, forward, and organize Microsoft Outlook mail via Microsoft Graph, with safe-by-default read-only operation and browser-based sign-in.
      11
      110 npm
      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

    B3.4/5.0

    Scored across 50 tools

    Disambiguation4/5

    Most tools map cleanly to a resource-action pair (messages, folders, rules, events, chats, channels), and shortcuts like archive_message and the batch_* tools are clearly specialized versions of move_message. The main overlap is update_message duplicating the read-state/flag conveniences (mark_read, flag_message, etc.), but the descriptions resolve it.

    Naming Consistency5/5

    Tool names follow a consistent snake_case verb_noun pattern with list_/get_/create_/update_/delete_ prefixes reused across resources. Exceptions like whoami and reply_all_message are still predictable and fit the overall style.

    Tool Count2/5

    50 tools is well above the typical well-scoped range, and even for a multi-domain Microsoft Graph server it feels heavy. The broad mail/calendar/Teams coverage gives the count some rationale, so it is 'too many' rather than an extreme mismatch.

    Completeness3/5

    Mail coverage is very complete with CRUD for messages, folders, rules, attachments, and bulk operations, and calendar events have full lifecycle support. However, Teams is effectively read-only with no send/create/update/delete for chats or channels, and calendar resources themselves cannot be created or deleted, leaving notable dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources