Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Microsoft 365 MCP Server

No user-submitted related servers found.

    Related Servers

    • Microsoft MCP

      0xka13b
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol servers for Microsoft 365, enabling AI assistants to interact with Calendar, Contacts, OneDrive, Outlook, and SharePoint via the Microsoft Graph API.
      MIT

    • Teams MCP

      hahsanayub
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server enabling AI assistants to interact with Microsoft Teams, users, chats, and organizational data via Microsoft Graph APIs.
      2,734 npm
      MIT

    • ms-graph-mcp

      CodyBuilder-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      A modular Model Context Protocol server for Microsoft Graph and Microsoft 365, enabling users to manage Teams, mail, calendar, To Do, contacts, and Outlook settings through natural language.
      50 npm
      ISC

    • Teams MCP

      floriscornel
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides AI assistants with access to Microsoft Teams, enabling interaction with teams, channels, chats, and organizational data through Microsoft Graph APIs.
      19
      2,734 npm
      139
      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

    C2.8/5.0

    Scored across 188 tools

    Disambiguation2/5

    Many tools have heavy overlap, particularly in calendar and mail listing: list-calendar-events, list-calendar-view-delta, list-calendar-event-instances, get-calendar-view, get-specific-calendar-view, and list-specific-calendar-events all return event collections with subtle differences. The 'specific' variants and default-vs-folder variants (create-outlook-contact vs create-contact-in-folder, list-outlook-contacts vs list-contact-folder-contacts) make misselection likely despite detailed descriptions.

    Naming Consistency3/5

    The dominant verb_noun pattern is consistent (create-, list-, get-, update-, delete-), but there are notable deviations: 'planner' vs 'plan' (create-planner-bucket vs list-plan-buckets), 'specific' inserted inconsistently (create-calendar-event vs create-specific-calendar-event), and tool names like graph-batch, login, parse-teams-url, and move-rename-onedrive-item break the pattern. Overall readable but not uniformly predictable.

    Tool Count1/5

    188 tools is an extreme count, far beyond the 25+ threshold for 'too many.' While Microsoft 365 covers many product areas, the surface is bloated with near-duplicate variants and could be consolidated significantly. This volume makes tool selection costly and error-prone for agents.

    Completeness3/5

    CRUD coverage is remarkably deep across mail, calendar, contacts, OneDrive, Excel, To Do, Planner, and OneNote. However, several tools referenced as critical in descriptions are missing from the actual tool set—notably list-users (referenced for resolving recipient emails), list-online-meetings, and get-schedule—which creates dead ends for common workflows like scheduling meetings or addressing mail.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources