← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionMCP AtlassianModel Context Protocol server for Confluence and JiraWhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS56 / 100 · C64 / 100 · C
Reliability7 / 2010 / 20
Security and permissions9 / 2012 / 20
Maintenance14 / 2012 / 20
Documentation14 / 2016 / 20
Setup experience12 / 2014 / 20
Best for
  • Teams that want an AI assistant to read and write Jira issues and Confluence pages directly
  • Organizations running both Atlassian Cloud and Server/Data Center environments
  • Developers who want JQL/CQL search, issue creation, and status transitions inside their IDE or chat client
  • 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 without an Atlassian Jira or Confluence account/instance
  • Scenarios requiring official Atlassian support guarantees (this is not an official Atlassian product)
  • Environments that cannot securely store or rotate API tokens/.env files
  • 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
  • URL(s) of the Jira and/or Confluence instance
  • Atlassian account email + API token (Cloud), or a Personal Access Token (Server/Data Center)
  • Whatever read/write permissions that account actually holds in Jira/Confluence (creating/updating issues, creating/updating pages, and adding comments require write access)
  • 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 or PAT can be used to read and write Jira/Confluence data as that account
  • The README explicitly warns to keep .env files secure to avoid credential exposure
  • Creating, updating, and transitioning issues, and creating/updating pages, are write operations — misconfigured automation could cause unintended data changes
  • Not officially maintained by Atlassian, so updates and security response depend on the community repository maintainers
  • 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, Autohand CodeClaude Code, Codex, Gemini CLI, Cursor
Tools1010