mcp-todoist
19 Todoist tools for Claude: tasks, subtasks, projects, labels and reminders, bulk edits and a dry-run mode.
- 246 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The Todoist token opens the whole account, and the tools create, change and delete tasks, projects and comments.
- Bulk operations touch many tasks in one call, and the dry-run mode is the only safeguard.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-todoistDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The Todoist token opens the whole account, and the tools create, change and delete tasks, projects and comments.
- Bulk operations touch many tasks in one call, and the dry-run mode is the only safeguard.
This is third-party code. Review the repository files before installing.
What it does
mcp-todoist connects Claude to Todoist and takes commands as plain phrases. Nineteen tools manage tasks, subtasks, projects and sections, labels, comments, filters and reminders, and the Pro and Business plans unlock filters, reminders and shared workspace labels. Quick add parses entries like Todoist itself: `#Project`, `@label`, `p1`, dates and deadlines in curly braces. Bulk tools create, update, complete and delete many tasks at once. Dry-run mode is switched on with the `DRYRUN=true` variable: reads go to the real API while changes are only simulated, and the log shows what would have happened. Separate tools show the activity log, productivity stats, completed tasks and backups.
Who it is for. Todoist users in Claude Desktop and Claude Code who need bulk operations and a trial mode instead of sorting tasks by hand.
Good fit when
- A project outline should become tasks with priorities, labels and due dates in one phrase.
- Before moving many due dates you want a dry run to show what would change.
- A task has grown and needs splitting into subtasks, or a subtask needs promoting to a main task.
- Labels have piled up and the agent should show usage stats and remove unused ones.
- A weekly review is built from the activity log and completed tasks.
Not a fit when
- You need the official Todoist server: this package is written by the community, not the company.
- The API token cannot be handed to a third-party package because it opens the whole account.
- Tasks must be read-only: the server has no separate read-only mode, and the dry run stands in for it.
Example request
Quick add: Review PR next Monday #Work @code-review p2 //Check error handlingMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
TODOIST_API_TOKENrequired, secret- A personal Todoist API token from the integration settings.
DRYRUN- The value true turns on the dry run: changes are only simulated.
Limitations
The server needs a personal Todoist API token in the `TODOIST_API_TOKEN` variable, and that token opens the whole account. Filters, reminders and shared workspace labels work only on Pro and Business plans. Deletion and bulk tools change real data unless you turned on `DRYRUN=true`. The server runs as a stdio process through `npx`, so Node.js is needed. Claude Desktop has an `.mcpb` bundle in releases where the token is entered in the install dialog. Detailed parameters of each tool are in `TOOLS_REFERENCE.md`.
How to disable. Run `claude mcp remove todoist` or delete the todoist block from the client configuration. Revoke the token in the Todoist integration settings.
FAQ
How do I connect mcp-todoist to Claude Code?
Run `claude mcp add todoist -e TODOIST_API_TOKEN=your_token -- npx @greirson/mcp-todoist`, substituting your token. For other clients add an `mcpServers` block with the `npx` command and the `@greirson/mcp-todoist` argument.
Where do I get a Todoist token?
In the Todoist settings, in the developer integrations section. Enter it when installing the `.mcpb` in Claude Desktop or put it into the `TODOIST_API_TOKEN` variable.
How do I test bulk edits without touching the data?
Add `DRYRUN=true` to the environment and restart the client. Reads go to the real API while creating, updating, completing and deleting are only simulated.
Which Todoist plans are needed?
Basic task and project management works on any plan. Reminders and filters need Pro or Business, and shared workspace labels need Business.
How do I add a task quickly with a phrase?
Use Todoist syntax: `#Project` for a project, `@label`, `p1` for priority, `//description` at the end and a deadline in curly braces. The quick add tool parses the entry the same way the app does.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server for Todoist: Claude creates, finds, edits, completes and deletes tasks from an ordinary phrase, with five tools
The official Todoist MCP server: the agent finds, creates and updates tasks and projects in your account
Things MCP: Things 3 tasks for an agent
Things MCP Server
An MCP server for Things 3 on Mac: Claude reads lists, searches tasks and creates or updates them, including in bulk.
MCP server for Super Productivity: an agent creates tasks, sorts them by project and tag, starts the timer and reads the worklog.
Microsoft To Do MCP gives an agent tasks with checklist items and recurrence rules for working on the user’s own plans.
Official Todoist command line with an agent skill: tasks, projects and inbox from the terminal
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| mcp-todoist (this card) | no | API key | 246 | |
| Todoist MCP Server | yes | OAuth | 561 | the official Todoist server for searching, creating and editing tasks; here nineteen tools, bulk operations and a dry run |
| Todoist MCP Server | no | API key | 392 | a five-tool server; here the scope is wider: subtasks, labels, filters, reminders and a dry-run mode |
| Todoist CLI | no | 330 | Todoist's official command line with a skill; here an MCP server that works right inside the Claude client |
README in short
Installation in Claude Desktop comes down to double-clicking the `.mcpb` file, and other clients use a command or a configuration block. The README collects example phrases for each tool group, a troubleshooting section and a description of the TypeScript code structure.