| FMRS | 62 / 100 · C | 64 / 100 · C |
|---|
| Reliability | 8 / 20 | 10 / 20 |
|---|
| Security and permissions | 11 / 20 | 12 / 20 |
|---|
| Maintenance | 13 / 20 | 12 / 20 |
|---|
| Documentation | 16 / 20 | 16 / 20 |
|---|
| Setup experience | 14 / 20 | 14 / 20 |
|---|
| Best for | - Existing Taskade users (personal or paid plans) who want an AI assistant to read and write their workspace directly
- Project/ops managers who want to bulk-manage projects, tasks, templates, and AI agents through a conversational interface
- Developers who want to reuse the OpenAPI codegen to quickly turn their own API specs into MCP tools
| - 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 | - Free-plan users needing full functionality — some endpoints (e.g. workspace listing) are gated on free accounts
- Anyone wanting to edit a published Genesis App's code or needing hosted OAuth access — that requires the separate Genesis App MCP at taskade.com/mcp, not this Workspace MCP
- Anyone wanting agents to reach third-party services like Slack, Shopify, or Gmail — that's handled by Taskade's MCP Connectors, not this server
| - 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 Taskade Personal Access Token (TASKADE_API_KEY) supplied as an environment variable, marked required and secret
- The token authorizes the server to call the Taskade public API (v1 and v2) on your behalf, with read/write access to workspaces, projects, tasks, agents, media, and webhooks
- In HTTP/SSE mode the key is passed as a query parameter (?access_token=), so consider the local network exposure
| - 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 | - The token has broad read/write scope; if leaked, an attacker could create, modify, or delete your Taskade tasks, projects, media, or agents
- Tools like agentPublicAccessEnable make an agent publicly accessible — use carefully to avoid unintentionally exposing internal content
- Webhook subscribe/unsubscribe tools can affect other automations relying on the same webhook; misuse can break existing integrations
- Per the README, the server only talks to Taskade's own API (api/v1 and api/v2) and does not send data to other third parties, but the API key should still be handled like any sensitive credential
| - 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 Desktop, Cursor, Windsurf, Cline, VS Code | Claude Code, Codex, Gemini CLI, Cursor |
|---|
| Tools | 62 | 10 |
|---|