Microsoft 365 MCP Server for Cloudflare Workers - provides MCP protocol access to Microsoft 365 services (Outlook, Calendar, Teams, Contacts) via Microsoft Graph API
This server implements 11 Microsoft 365 integration tools with HTTP/SSE transport. Tool naming follows verb_noun conventions consistently (sendEmail, getEmails, createCalendarEvent, etc.), which is good. All tools have descriptions present. However, critical gaps exist: parameter descriptions are minimal or missing for several inputs, schemas lack proper type information and validation rules, output schemas are not documented, and error handling is generic without recovery guidance. The server demonstrates functional tool composition and reasonable parameter constraints (enum for contentType, max limits on numeric params), but falls short of production-grade quality due to incomplete parameter documentation, missing output schema specifications, and lack of actionable error messages. Schema documentation is the weakest dimension, tools accept parameters without documenting return structures, making it difficult for LLMs to plan downstream operations.
Create calendar event
Create Teams online meeting
Get calendar events
Get list of calendars
Get contacts
Get recent emails
Get list of Teams the user belongs to
Output schemas not documented. Tools return data structures to the LLM but callers cannot see what fields to expect or how to chain calls. For example, getEmails should document whether it returns [id, sender, subject, body, timestamp] and whether subsequent tools should use the returned email_id or some other identifier.
Parameter descriptions are missing or generic. 'Recipient email address' is good, but many params lack actionable guidance. For example, getEmails folder param only says 'Mail folder', valid values (inbox, sent, drafts, etc.) are not documented. searchEmails query parameter lacks format hints (boolean operators? regex? exact match?).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 60 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Get current user profile
Search emails
Send an email via Outlook
Send a message to Teams channel
No error handling or recovery guidance visible in tool definitions. If sendEmail fails (invalid recipient, quota exceeded, auth timeout), the tool likely returns a generic error with no actionable next steps for the LLM (e.g., 'Try search_users() first to validate the recipient').
Destructive operations (sendEmail, createCalendarEvent, createTeamsMeeting, sendTeamsMessage) lack confirmation or dry-run support. Agents can make mistakes, there is no pattern for 'preview' or 'confirm before execute'.
Parameter type definitions incomplete. sendEmail contentType uses enum (good), but most numeric parameters (count, days, max) lack type declarations visible in the definition. If the schema is inferred from code rather than explicit JSON Schema, scores are capped.
No pagination guidance for list operations. getEmails and getContacts both accept count parameters (max 50 and max 100 respectively) but do not document how to fetch beyond the limit or whether a next_cursor exists for continuation.
Attendee parameters in createCalendarEvent and createTeamsMeeting accept email arrays but do not specify whether they should be '[email protected]' or display names or both, and whether the tool auto-validates/resolves them or returns errors for invalid addresses.