Microsoft 365 Outlook Mail and Calendar Model Context Protocol (MCP) server for Claude and AI assistants with local Windows MAPI bridge
Server has 7 tools with complete schemas and descriptions. Naming follows verb_noun pattern (outlook_*). Descriptions are present but generic (avg 95 chars, below 194 baseline). Parameters have types and descriptions. Critical gaps: no output schemas documented, no error recovery guidance, no parameter constraints (enums), and missing security annotations. outlook_send_mail has a confirm_send safety gate (good), but no dry-run pattern. Error handling returns raw exception strings instead of actionable guidance.
Check Microsoft 365 Outlook authentication and connection status
Create an email draft in Outlook Drafts folder (recommended method for Human-in-the-Loop review)
Get full details and content of a specific email message by its ID. Content is safely encapsulated.
List upcoming calendar events and meetings from Outlook
List recent emails from an Outlook mail folder (e.g. inbox, sentitems, archive, drafts)
Search emails across the mailbox using query terms, sender, subject, etc.
No output schemas documented. LLMs cannot infer response structure (fields, types, pagination). Forces agents to guess what data is available.
Error handling returns raw exception strings (e.g. 'Error listing messages: {str(e)}'). No recovery guidance, no error classification (retryable vs fatal). LLM cannot determine next action.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Server declares risk levels in metadata but tools lack MCP-standard annotations for agent safety.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
Send an email through Outlook. Requires confirm_send=True for Human-in-the-Loop safety; otherwise creates a draft.
Parameter 'folder' in outlook_list_messages accepts free-form strings (inbox, sentitems, archive, drafts). Should be an enum to prevent hallucinated folder names.
outlook_send_mail description mentions 'confirm_send=True for Human-in-the-Loop safety' but does not explain what happens if False (creates draft). Ambiguous behavior.