Skip to main content
Glama

Related Servers

Alternatives to microsoft365-mcp-server

Related Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that gives Claude Code (or any MCP client) controlled access to Microsoft 365 through the Microsoft Graph API: mail, calendar, contacts, files, notes, tasks, Teams, SharePoint, and the full tenant-admin surface.
    25 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Remote MCP server for Microsoft Graph with delegated OAuth support, enabling interaction with Microsoft 365 services like mail, calendar, OneDrive, SharePoint, Teams, and more via natural language.
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    A CLI and MCP server for Microsoft Outlook and OneDrive via the Microsoft Graph API, enabling AI agents to manage email, calendar, contacts, tasks, and files through the Model Context Protocol.
    23
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    A production-ready MCP server that provides secure, delegated access to Microsoft 365 services including Email, SharePoint, OneDrive, and Calendar. It enables AI models to search messages, browse files, manage calendar events, and parse document contents using OAuth 2.1 authentication.
    MIT
  • A
    license
    B
    quality
    A
    maintenance
    A Model Context Protocol server that enables interaction with Microsoft 365 services (Excel, Calendar, Mail, OneDrive, Teams, etc.) through the Graph API, allowing AI assistants to manage Microsoft 365 resources via natural language.
    203
    125,353 npm
    1,140
    MIT

TDQS

B3.1/5.0

Scored across 97 tools

Disambiguation3/5

The set covers many distinct M365 workloads, but several tools overlap heavily: list_messages, scan_messages, search_messages, and summarize_senders all operate on mail, while download_file, read_document, get_drive_item, and search_files overlap in file access. Descriptions usually clarify when to use each, but the sheer number of near-neighbors makes misselection likely.

Naming Consistency5/5

Names are uniformly snake_case and almost always follow a verb_noun pattern such as list_messages, create_event, update_todo_task, and search_site_files. Variants like graph_query and get_me are minor exceptions but do not break the overall convention.

Tool Count2/5

97 tools is far too many for reliable agent selection, even for a broad Microsoft 365 server. The surface covers many domains, but operations could be consolidated or grouped to reduce context burden and selection error.

Completeness4/5

Coverage is broad across mail, calendar, contacts, OneDrive, SharePoint, Teams, Planner, OneNote, To Do, users/groups, and auth, with graph_query as an escape hatch. Some lifecycle gaps remain, such as file/folder delete or move, planner task deletion, and team/channel creation, but core workflows are covered.

Maintenance

ActivityActive
ResponsivenessNo recent community issues