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.

DimensionAtlassian Dc MCP JiraMCP server for Atlassian Jira Data CenterWhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS60 / 100 · C64 / 100 · C
Reliability9 / 2010 / 20
Security and permissions15 / 2012 / 20
Maintenance8 / 2012 / 20
Documentation14 / 2016 / 20
Setup experience14 / 2014 / 20
Best for
  • Organizations using Atlassian Jira Data Center
  • Teams that want to manage Jira issues via AI assistants
  • Users needing on-premise or private integration with Jira
  • 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
  • Users of Jira Cloud (non-Data Center)
  • Those requiring official support or warranty
  • Users without a Jira Data Center instance or API token
  • 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 Jira Personal Access Token (PAT)
  • Permissions depend on token scopes configured in Jira
  • Typically needs read permissions for viewing issues and write permissions for creating
  • 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
  • Token could be leaked if stored in plain text config files
  • Community-maintained project may lack timely security updates
  • Overprivileged PATs could pose risks to the Jira instance
  • 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, Claude CodeClaude Code, Codex, Gemini CLI, Cursor
Tools010