| FMRS | 64 / 100 · C | 66 / 100 · C |
|---|
| Reliability | 10 / 20 | 8 / 20 |
|---|
| Security and permissions | 12 / 20 | 15 / 20 |
|---|
| Maintenance | 12 / 20 | 15 / 20 |
|---|
| Documentation | 16 / 20 | 15 / 20 |
|---|
| Setup experience | 14 / 20 | 13 / 20 |
|---|
| Best for | - 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
| - Developers, content creators, and project teams using Atlassian Cloud
- Teams that want Atlassian access inside ChatGPT, Claude, Cursor, or VS Code
- Users who need natural-language search, write, and cross-product workflows
|
|---|
| Not for | - 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
| - Users without an Atlassian Cloud site or relevant product permissions
- Deployments requiring a self-hosted MCP server
- Users unwilling to grant an AI client access to Atlassian data or actions
- Jira Service Management or Bitbucket Cloud workflows requiring OAuth authentication
|
|---|
| Required 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)
| - Jira and Confluence provide read, write, and search permission groups
- Jira Service Management provides read and write access through API tokens only
- Bitbucket Cloud provides read and write access through scoped API tokens only
- Compass is available through OAuth 2.1 only
- The first OAuth installer for a site must have access to the Atlassian apps requested by the MCP scopes
- Organization administrators can manage domain controls, API-token authentication, app access, and audit logs
|
|---|
| Risks and side effects | - 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
| - AI clients can perform Jira, Confluence, Jira Service Management, Bitbucket, and Compass actions on the user’s behalf
- Prompt injection, indirect prompt injection, and tool-poisoning attacks may cause data exfiltration or unintended changes
- Use least privilege, scoped tokens, and minimal project or workspace access
- Require human confirmation for high-impact or destructive actions and monitor audit logs
|
|---|
| Supported clients | Claude Code, Codex, Gemini CLI, Cursor | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 10 | 0 |
|---|