graph-mcp
Related Servers
Alternatives to graph-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides read-only access to Microsoft 365 services including SharePoint, OneDrive, Outlook, Teams, and Calendar through the Microsoft Graph API, enabling users to search, browse, and retrieve content across their M365 suite.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to personal Microsoft Outlook mail, calendar, and contacts via the Microsoft Graph API using device-code authentication, without requiring the Outlook desktop app.MIT
- AlicenseNot gradedqualityDmaintenanceProvides read-only access to classic desktop Outlook mailbox and calendar on Windows, enabling safe email and calendar queries without any write capabilities.MIT
- AlicenseNot gradedqualityBmaintenanceEnables interacting with Microsoft 365 and Office services through the Microsoft Graph API, covering email, calendar, files, Teams, SharePoint, contacts, tasks, and related organizational resources with authentication, read-only, and tool-filtering options.MIT
- AlicenseAqualityCmaintenanceEnables read-only search and export of Outlook emails and attachments with a chain-of-custody manifest for evidence collection.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Microsoft 365 and Office services through the Graph API, covering email, calendar, files, tasks, contacts, Teams, SharePoint, and more with configurable read-only and tool-filtering controls.MIT
TDQS
Scored across 15 tools
Each tool is scoped to a single domain and action, with domain prefixes (mail_, onedrive_, onenote_, calendar_, contacts_) making boundaries obvious. Within a domain, pairs like mail_list vs mail_search vs mail_get vs mail_attachment target clearly different retrieval modes, so an agent can pick correctly without guessing.
The dominant pattern is domain_noun/action in snake_case (mail_get, mail_folders, onedrive_read, onenote_pages, calendar_events), applied consistently across all five domains. The only outlier is `whoami`, which follows neither the prefix nor the verb_noun convention, a minor deviation in an otherwise predictable scheme.
Fifteen tools is squarely in the well-scoped range, and the surface is balanced across mail (5), OneDrive (4), OneNote (3), calendar (1), contacts (1) plus whoami. Every tool covers a distinct retrieval need with no filler or redundant variants.
The read-only surface is coherent and covers the core workflows: discover, search, list and read content across mail, files, notebooks and calendar. Gaps remain for a read-only model — no single-calendar-event fetch, no contact lookup by full detail beyond name prefix, and no mail thread/conversation view — but agents can work around these with the existing tools.