← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionM365 Assistant MCP ServerMCP server connecting Claude to Microsoft 365WhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS42 / 100 · D64 / 100 · C
Reliability5 / 2010 / 20
Security and permissions9 / 2012 / 20
Maintenance4 / 2012 / 20
Documentation13 / 2016 / 20
Setup experience11 / 2014 / 20
Best for
  • Developers needing integration between Microsoft 365 and AI assistants
  • Individuals wanting natural language control of Outlook and OneDrive
  • Teams automating email and calendar management
  • Individuals who want to talk to Claude from their personal WhatsApp number
  • Developers comfortable configuring from a terminal and using the Claude Code development flag
  • Automation scenarios needing remote tool approval from a phone
Not for
  • Organizations with strict security requirements against third-party servers
  • Users needing deep integration with Microsoft Teams or SharePoint (not supported)
  • Beginners wanting a plug-and-play solution without Azure configuration
  • Compliance scenarios requiring the official WhatsApp Business API or a Meta developer account
  • Teams needing officially hosted, multi-tenant, or cloud multi-instance deployment
  • Environments unable to guarantee only one client instance at a time
  • Users expecting voice transcription without setting up mlx-whisper themselves
Required permissions
  • Microsoft Graph delegated permissions: offline_access, User.Read, Mail.ReadWrite, Mail.Send, Calendars.ReadWrite, Files.ReadWrite
  • Power Automate API scope (optional): https://service.flow.microsoft.com//.default
  • Local file system: tokens stored in ~/.outlook-mcp-tokens.json
  • Read and send WhatsApp messages as your personal number
  • Access the local runtime state directory ~/.whatsapp-channel/ (auth, allowlists, group configs, inbox)
  • Read and write local repository files and run scripts (e.g. bun scripts/access.ts, scripts/watchdog.sh)
  • Optional local voice transcription (ffmpeg and an mlx-whisper environment)
Risks and side effects
  • OAuth tokens stored in plaintext locally, risk of exposure
  • Azure app registration required, misconfiguration can break service
  • Power Automate integration limited to solution-aware flows with manual triggers
  • Third-party server may introduce supply chain risk
  • Messages Claude sends appear from your own number and are indistinguishable to recipients
  • WhatsApp allows one linked-device session per account; running two servers makes them kick each other off
  • Access-control commands are deliberately not MCP tools (terminal-only); exposing them to the message side risks prompt injection
  • Session waking depends on the Claude Code channel extension; other clients get no push
  • A known Claude Code client bug (#37933) may cause messages not to arrive, a client-side issue
  • Launching with --dangerously-load-development-channels carries risk, so verify the source is trustworthy
Supported clientsClaude DesktopClaude Code, Codex, Gemini CLI, Cursor
Tools2810