M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

Dimensionmonday.com MCP ServerConnect AI agents securely to the monday.com Work OSWhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS55 / 100 · C64 / 100 · C
Reliability9 / 2010 / 20
Security and permissions4 / 2012 / 20
Maintenance13 / 2012 / 20
Documentation15 / 2016 / 20
Setup experience14 / 2014 / 20
Best for
  • Teams already using monday.com for project/task management who want AI-driven board operations
  • Developers connecting AI agents to structured work data for task automation
  • Users who prefer the officially hosted service over local setup
  • 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
  • Teams not using the monday.com platform
  • Fully offline environments (even local mode requires network access to the monday.com API)
  • Cases needing read-only guarantees without explicitly enabling read-only mode
  • 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
  • Requires a monday.com API token (personal access token or OAuth) to act on the user's account
  • Default mode grants read/write access — can create, modify, and delete boards/items/columns, so token scope should be handled carefully
  • Dynamic API Tools require full API access and are incompatible with read-only mode
  • 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
  • A leaked API token exposes read/write access to all boards under that account
  • Write tools such as delete_item and delete_column can cause irreversible data loss
  • Dynamic API Tools allow arbitrary GraphQL queries/mutations, widening the potential blast radius of misuse
  • 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 Desktop, Cursor, Gemini CLI, ChatGPT, Microsoft Copilot StudioClaude Code, Codex, Gemini CLI, Cursor
Tools1710