Todoist Extended MCP Server

Todoist Extended MCP server exists for a simple reason — assistants are far more useful when they can act on Todoist Extended directly instead of describing what you should do. Todoist MCP Server Extended - Enabling natural language management of todoist via Claude, MCP and todoist REST APIv2. Featuring LLM optimized Tools including batch operations and robust error handling.

What you get

An MCP (Model Context Protocol) server implementation that integrates Claude - or any MCP compatible LLM if you're crafty - with Todoist, enabling natural language task management via MCP tools. The tools in this server allows Claude to interact with your Todoist tasks, projects, sections, and labels using everyday language, while also optimized for LLM workflow efficiency.

• Task Management — Create, update, complete, and delete tasks using everyday language
• Label Management — Create, update, and manage personal labels and task labels
• Project Management — Create, update, and manage Todoist projects
• Section Organization — Create and manage sections within projects
• Smart Search — Find tasks and labels using partial name matches
• Flexible Filtering — Filter tasks by project, section, due date, priority, and labels

Configuration and credentials

You will need one environment variable: TODOIST_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by Chrusic; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the todoist extended mcp server does with a few real requests.