No user-submitted related servers found.
Scored across 103 tools
The toolset is organized by domain and descriptions are highly detailed, but with 103 tools there are several near-overlapping pairs (list-calendar-events vs get-calendar-view, search-drive-items vs search-my-drive, search-people vs search-users/list-users) that create selection risk. The explicit 'primary' and 'prefer' notes reduce ambiguity somewhat, but the sheer number of similar retrieval variants makes it hard for an agent to always pick the right one.
Tool names consistently use kebab-case verb-noun phrasing, and domain prefixes like mail-, calendar-, team-, onenote-, and site- make the hierarchy fairly predictable. Minor inconsistencies exist such as get-calendar-view vs list-calendar-events, search-drive-items vs search-my-drive, and the long shared-mailbox variants, but there is no chaotic mixing of naming conventions.
103 tools is an extreme count, especially for a server named m365-reporting-mcp, which implies a reporting focus rather than a full Microsoft Graph client surface. This exceeds the '50+ tools' threshold for extreme mismatch, even though each tool maps to a real Graph operation.
The server covers a remarkably broad set of M365 data sources: mail including shared mailboxes, calendar, Teams chats/channels/meetings/transcripts/recordings, OneNote, SharePoint/OneDrive, Loop, people, users, and audit logs. Minor gaps exist, such as no event-attachment content download, no shared-mailbox draft sending, and no direct channel keyword search, but these are documented with workarounds and the core reporting/read workflows are well covered.