← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionHackMD MCP ServerA Model Context Protocol server for integrating HackMD's note-taking platform with AI assistants.WhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS58 / 100 · C64 / 100 · C
Reliability7 / 2010 / 20
Security and permissions10 / 2012 / 20
Maintenance12 / 2012 / 20
Documentation15 / 2016 / 20
Setup experience14 / 2014 / 20
Best for
  • Developers who want to integrate HackMD note management into AI workflows
  • Individuals or teams who prefer natural language interaction with their notes
  • Users who need cloud deployment of MCP servers
  • 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
  • Not suitable for users without a HackMD API token
  • Not suitable for offline access to notes (server depends on network API)
  • Not for scenarios requiring advanced collaboration features like real-time co-editing, as the server provides mainly CRUD operations
  • 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 HackMD API token (HACKMD_API_TOKEN) to authenticate all operations
  • Server can read and modify user profile, notes, teams, history, etc., depending on token permissions
  • 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
  • API token leakage could lead to unauthorized account access; never commit it to version control
  • For HTTP transport, if the server is hosted without endpoint protection, anyone could use your token
  • Server modifies user data (create, update, delete notes); confirm before operations
  • 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
Tools1210