| FMRS | 61 / 100 · C | 64 / 100 · C |
|---|
| Reliability | 9 / 20 | 10 / 20 |
|---|
| Security and permissions | 10 / 20 | 12 / 20 |
|---|
| Maintenance | 13 / 20 | 12 / 20 |
|---|
| Documentation | 16 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - Existing Todoist users or teams who want to manage tasks and projects through conversation with Claude
- Users who need to run bulk task operations (e.g., mass priority updates, clearing overdue tasks)
- Developers who want to validate automations in Dry-Run mode before touching real data
| - 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 don't use Todoist, or who need to connect to other task tools like Jira or Asana
- Enterprise scenarios requiring an official Todoist product or SLA-backed support
- Highly privacy-sensitive setups that don't want API tokens and task data routed through a third-party MCP 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 personal Todoist API token (from Todoist developer settings), which grants account-level read/write access
- Can read and modify all account data including tasks, projects, sections, labels, comments, reminders, filters, notes, and shared labels
- Some features (reminders, filters, shared labels) require a Todoist Pro or Business subscription
| - 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 | - This is a third-party open-source project maintained by an individual developer, not an official Todoist product
- The API token is stored in plaintext in the client config file and should be protected from exposure
- Bulk delete or bulk complete operations can make irreversible changes to real Todoist data if misconfigured; test with DRYRUN=true first
- Task and comment content passes through Claude, so users with sensitive data should evaluate their own data-flow risk
| - 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, Claude Code | Claude Code, Codex, Gemini CLI, Cursor |
|---|
| Tools | 19 | 10 |
|---|