Todoist

Name: Todoist MCP Server
Availability: InStock
Author: Todoist

Productivity27 tools

Triage your inbox, plan your week, create projects and complete tasks from your AI assistant. 27 tools listed, OAuth sign-in, one combined read-and-write scope, works on every Todoist plan.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Todoist via MCP

https://ai.todoist.net/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Todoist Tools & Capabilities (27)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

Deleting a task is permanent. Todoist documents no undo and no restore for a deleted task. The connector exposes a delete tool and no inverse. Backup import is the only documented recovery, it is a paid-plan feature, and backups are daily — so same-day work can be unrecoverable. This is the single most important sentence on the page.
The consent screen cannot narrow the connection. One scope, data:read_write, with reading and writing fused into the same grant. A read-only Todoist connection is not something you can approve here, even though data:read exists on the platform and Doist's own CLI uses it.
The directory listing understates the surface by twenty tools. Doist's source registers 47; Anthropic's listing names 27. Labels, filters, reminders, templates, analytics, reordering and attachments are entirely absent from the listing, as are reschedule-tasks and uncomplete-tasks.
Todoist's own capability table contradicts the tool list. Todoist's Claude connector article lists managing sections, labels, comments and filters under what Claude "doesn't support", while the same directory listing names add-sections, update-sections, add-comments and update-comments. We cannot reconcile these from published sources. Treat the tool list as the ceiling and the help article as the vendor's own expectation, and verify against your account.
It cannot put a new project in a workspace folder. Todoist states this directly in two separate articles: create the project, then move it into the folder by hand.
Changing a date destroys recurrence. Doist's server instructions say update-tasks replaces the whole due string, which wipes the repeat pattern on a recurring task. The tool that preserves it, reschedule-tasks, is one of the twenty absent from Anthropic's listing.
Template imports write immediately and cannot be undone. Doist's own server instructions say so. import-project-template is in the source and not in the directory listing.
History is plan-gated. Todoist documents one week of activity history on Beginner and full history on Pro and Business. An assistant asked what you finished last month will simply have less to read on a free account.
Structural caps apply on every plan. Todoist documents 300 active tasks per project, 20 sections per project, 500 total active projects and 500 labels per account, and states these apply to Pro and Business too with no option to raise them. A bulk operation driven conversationally can reach them.
Rate limits are per user, not per connector. Todoist documents 1,000 partial sync requests and 100 full sync requests per user per 15-minute period, with a 15-second processing timeout on a standard request. Todoist does not state how MCP tool calls map onto these counters, so treat the figures as platform-wide rather than connector-specific.
The delete scopes are unexplained. Todoist's platform documents data:delete and project:delete as scopes separate from data:read_write. The MCP descriptor advertises neither, yet the connector ships a delete tool. We did not authenticate and make no claim about how the server resolves this. Read the consent screen.
There is no public tool catalogue. A GET to https://ai.todoist.net/mcp returns HTTP 405 with Allow: POST, and the host root, robots.txt and .well-known/mcp.json all return 404. The names-only tool section is a limit of the server, not of our effort.
We did not read the live tools and never called one. Our only contact with the server was an anonymous handshake that returned HTTP 401, plus reads of its two .well-known documents. Everything above about tool behaviour comes from Todoist's documentation, Doist's published source, or Anthropic's directory listing.

Frequently asked questions

Which Todoist plan do you need for the MCP server?

Every plan, including the free Beginner tier. Todoist's help documentation names no plan requirement for the connector itself. What your plan changes is how much history the connector can read: Todoist documents one week of activity history on Beginner and full history on Pro and Business, so a Beginner account cannot answer questions about last month.

Can the Todoist MCP server permanently delete my tasks?

Yes, and a deleted task cannot be restored. Todoist states plainly that once a task is deleted it cannot be restored to your project, and that there is no undo option for a task deletion. The only recovery path Todoist documents is importing a copy from a backup, which is a Pro and Business feature.

Why does the Todoist connector sign you in at a different domain than the server?

The server and the login live on different hosts by design. The connector endpoint is ai.todoist.net, but its OAuth descriptor names https://todoist.com as the authorization server. So the sign-in page you approve is on Todoist's own brand domain, even though the MCP host is not.

Can you give the Todoist connector read-only access?

Not through this server. Its descriptor advertises one scope, data:read_write, which fuses reading and writing into a single grant. Todoist's platform does publish a separate read-only data:read scope, and its own command-line tool offers a read-only login, but the MCP resource does not request that narrower scope.

Why did asking Claude to change a date break a recurring Todoist task?

Changing the date replaces the whole due string, which destroys the repeat schedule. Todoist's guidance is to say reschedule rather than change the date, because the reschedule path keeps the recurrence intact. If the recurrence is already lost, Todoist says to reopen the task and set the repeat in the date field again.

Why can't Claude find your completed recurring tasks in Todoist?

Recurring tasks never enter your completed list. Todoist explains that completing a recurring task reschedules it to the next occurrence instead of marking it done, and records the event in your activity log. Todoist's fix is to name the activity log in your request, which returns every completion in the period.

How many tasks can the Todoist MCP server create in one request?

Twenty-five. Todoist documents that the MCP server supports up to 25 tasks per call and recommends telling the assistant to add them all together. Todoist warns that creating tasks one at a time can exhaust the assistant's tool-call budget before a long list is finished.

Why does the Todoist connector show as Requested and never finish connecting?

A Claude workspace administrator has not approved it yet. Todoist documents that on Claude Team and Enterprise plans an Owner or Primary Owner must approve a connector request before a member's connection completes. Todoist notes there is nothing to approve on the Todoist side, so the block is entirely on the Claude account.