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
      D
      maintenance
      A Model Context Protocol server enabling AI assistants to interact with Microsoft Teams, users, chats, and organizational data via Microsoft Graph APIs.
      1,223 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.
      12 npm
      ISC

    • Teams MCP

      floriscornel
      A
      license
      A
      quality
      A
      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
      1,223 npm
      146
      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 200 tools

    Disambiguation2/5

    The set contains many near-duplicate listing and event tools with subtle distinctions (list-calendar-events vs get-calendar-view vs list-specific-calendar-events vs get-specific-calendar-view; list-mail-messages vs list-mail-folder-messages vs read-mail-text; create-calendar-event vs create-specific-calendar-event). Descriptions and tips clarify some boundaries, but an agent must track default-vs-specific calendar/folder and delta/view semantics, making misselection likely.

    Naming Consistency4/5

    Most tools follow a predictable verb_noun kebab-case pattern (list-..., get-..., create-..., update-..., delete-...). Minor deviations such as login, logout, select-account, graph-batch, move-rename-onedrive-item, and compound Graph-resource names exist, but the convention is generally readable and consistent.

    Tool Count1/5

    With 200 tools, the surface is far beyond a well-scoped set and contains many redundant variants across mail, calendar, contacts, files, Excel, OneNote, Planner, and To Do. Even for a broad Microsoft 365 server, this count makes discovery and tool selection costly and error-prone.

    Completeness2/5

    Many resources have full CRUD, but there are significant gaps: list-users is repeatedly referenced in tips but absent, list-online-meetings is referenced but absent, OneNote page update is missing, and Teams/SharePoint coverage is thin. These dead ends will cause agent failures in common workflows.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources