| FMRS | 47 / 100 · D | 64 / 100 · C |
|---|
| Reliability | 5 / 20 | 10 / 20 |
|---|
| Security and permissions | 9 / 20 | 12 / 20 |
|---|
| Maintenance | 9 / 20 | 12 / 20 |
|---|
| Documentation | 12 / 20 | 16 / 20 |
|---|
| Setup experience | 12 / 20 | 14 / 20 |
|---|
| Best for | - Users who want Notion, Monday, Airtable, Jira, Slack, and similar tools inside MCP hosts like Claude, Cursor, Cline, or WindSurf
- No-code users who prefer not to install and maintain a local server
- Teams wanting a single hub for multiple productivity integrations
| - 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 who need a local stdio server (the local version is deprecated)
- Apps not among the supported providers and not covered by an integration request
- Security-sensitive environments unwilling to delegate credentials to a third-party cloud hub
| - 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 | - OAuth2-style account access authorization to supported apps such as Notion, Monday, Airtable, Jira, Slack, Google Drive, Office 365, Miro, Intercom, and PayPal
| - 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 | - Credentials and data pass through the WayStation cloud service, a third-party hosted platform
- OAuth2 scopes per app may be broad; connect with least privilege
- Granting cloud access to work accounts requires evaluating compliance and data residency requirements
| - 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 clients | Claude, Cursor, Cline, Windsurf | Claude Code, Codex, Gemini CLI, Cursor |
|---|
| Tools | 0 | 10 |
|---|