Searching for Todoist MCP turns up four different things. Todoist ships a one-click connector for Claude, a separate MCP server with more features, and two community servers are still on GitHub. Each page tells you how to install its own option and says little about the other three.
That matters because these are your tasks. One of the four can delete a project, and one will strip the repeat schedule off a recurring task if you phrase a request slightly wrong. The official server also puts 47 tools in your context window before you ask anything.
If all you want is to add and reschedule tasks from a Claude chat, the connector is enough. If you need labels, comments, filters, reminders or delete, you want the official server.
- Use the official server at
https://ai.todoist.net/mcp. It is first-party, remote, and OAuth-based. - It ships 47 tools. That is thorough, and every tool definition sits in your context. ContextBolt has a far smaller surface and covers the reading your tasks came from.
- The Claude connector is the lighter option and cannot delete anything, which is often a feature.
- The free Beginner plan caps you at 5 personal projects, and the MCP caps you at 25 tasks per call.
- Skip both community servers. They work, but the vendor now ships its own.
Which Todoist MCP should you use?
Here are the four options, checked against the repositories and Todoist’s own help pages.
| Option | What it is | Auth | Use it? |
|---|---|---|---|
| Official MCP server | Remote server, 47 tools, actively maintained | OAuth | Yes |
| Claude connector | One-click: read, create, update, complete | OAuth | Yes, if that is enough |
greirson/mcp-todoist | Local server, 19 consolidated tools, last commit March 2026 | API token | No |
stanislavlysenko0912/todoist-mcp-server | Local server, REST plus Sync API, last commit April 2026 | API token | No |
Start with the connector. It takes one click, covers add, update, complete and reschedule, and cannot delete your work. Live with it for two weeks. For many people that covers it, because what they wanted was to stop opening a second app to capture a task.
Move to the official MCP server when you hit a wall the connector was built with. Usually that’s labels or filters, sometimes cleanup work that needs delete.
What can the Todoist connector for Claude do?
According to Todoist’s own connector documentation, the connector lets Claude read tasks and projects, create them, update them, and complete them. It stops there. It cannot do these:
- Delete anything: No tasks, no projects.
- Manage sections, labels, comments or filters: If your system runs on labels, the connector can’t see half of it.
- Assign tasks in shared projects: Solo use only.
- Move a project into a team workspace folder, or reorder projects in the sidebar.
One documented behavior is worth remembering. Ask the connector to “change the date” on a recurring task and it removes the repeat schedule. Ask it to “reschedule” and the recurrence survives. One word separates adjusting a routine from deleting one, and nothing in the interface warns you.
The connector’s limits are mostly right. An agent that can’t delete your tasks can’t have a bad day at your expense.
How to set up the official Todoist MCP
The server is remote, so there is no npm package to install and nothing to keep updated. For Claude Code, run one command.
claude mcp add --transport http todoist https://ai.todoist.net/mcp
- Run the command above.
- Ask the agent to do something with Todoist. The first Todoist tool call opens a browser window and asks you to grant access.
- Approve it. There is no API token to paste and no environment variable to export.
- Ask the agent to list your Todoist projects. If it answers, you’re connected.
Todoist also publishes a Claude Code plugin route, which is the path it recommends. Any other client that speaks streamable HTTP can point at the same URL, and the package also runs standalone with npx @doist/todoist-mcp.
Two limits to know up front. The server handles a maximum of 25 tasks per call, so a brain dump of forty items becomes two calls. And projects can’t be created directly inside a workspace folder. They have to be moved afterward.
What does it cost?
The MCP server is free. Todoist’s plan limits are what bite.
The free Beginner plan allows 5 personal projects. That sounds fine until an agent with add-projects available decides your brain dump deserves its own project structure. Todoist’s Pro plan raises that to 300 personal projects, and Business adds team projects on top.
Claude Code itself needs a paid Claude plan, which Todoist’s setup article states directly. The connector route has no such requirement.
Why does the official server use so much context?
I counted the tool files in the official repository and there are 47. add-tasks, find-tasks, update-tasks, complete-tasks, uncomplete-tasks, reschedule-tasks and delete-object are all separate definitions, and that is before the full set each for projects, sections, labels, comments, filters and reminders, plus get-productivity-stats, get-project-health, analyze-project-health, get-workspace-insights and export-project-template.
Every tool definition is text in your context window before the conversation starts. Anthropic’s engineering write-up on advanced tool use puts numbers on it. A five-server setup with 58 tools consumes roughly 55,000 tokens before anyone types anything, with GitHub’s 35 tools alone accounting for about 26,000. Anthropic says it has seen tool definitions reach 134,000 tokens before optimization.
I have not metered Todoist’s 47 myself, so treat this as an order of magnitude rather than a measurement. It is still a meaningful slice of the window you wanted for your actual work.
The fix is arriving on the client side. Anthropic’s Tool Search Tool keeps the tool index outside the context window and loads only the definitions the model reaches for, cutting definition tokens by around 85% while improving tool-selection accuracy from 79.5% to 88.1% on Opus 4.5. If your client supports deferred tool loading, turn it on before you connect anything this large.
Until then, don’t run every MCP server you own at once. Connect Todoist in the sessions where you’re planning, and turn it off in the sessions where you’re coding. Other vendors draw the line elsewhere: Trello’s server launched with a small tool set, and ClickUp’s is wide and metered by the day.
Do the community servers still make sense?
For two cases.
stanislavlysenko0912/todoist-mcp-servercovers Todoist’s Sync API alongside REST, and it injects your projects and labels into the server instructions so the model doesn’t burn a tool call discovering them.greirson/mcp-todoistdoes bulk create, update, delete and complete through consolidated tools, with in-memory caching, on your machine against your own token. Consolidating six task actions into onetodoist_tasktool is a smarter design than the official server’s.
For everyone else, neither uses OAuth, so you’re pasting a long-lived API token into a config file, and neither has a vendor behind it. A first-party server with OAuth and active commits beats a community server that hasn’t had a commit in months. The same logic applies to picking any MCP server: check the last commit date before the feature list.
An agent with write access to your task list can reorganize it faster than you can read the diff, so think before you approve the OAuth prompt. We covered how to vet an MCP server in more detail.
Where does ContextBolt fit?
ContextBolt has nothing to do with Todoist and does not integrate with it. The two sit either side of the same gap. Todoist holds what you decided to do. ContextBolt holds what you decided was worth keeping: web pages you saved, and posts you saved on X, Reddit and LinkedIn.
Its bookmark server ships six tools, not 47: search_bookmarks, list_clusters, get_cluster_bookmarks, get_recent_bookmarks, export_bookmarks and save_bookmark. That was deliberate, because a server you run in every session has to be cheap to have running.
Basic is free and capped at 150 bookmarks. Pro is $6 a month, removes the cap, and adds cloud sync and an MCP endpoint, so Claude can read that library in the same chat as your task list.