Todoist MCP

What it does

Todoist MCP is Doist's own server for a Todoist account, talking to the Todoist API. You get tasks (add, update, complete, reopen, reschedule, search by text or date, list completed ones), projects, sections, comments, labels, saved filters and reminders. On top of that come task assignment in shared projects, activity history, productivity stats, project health summaries, workspace listings and project templates for export and import. Many tools accept a batch of items in one call.

Two programs ship in the npm package. todoist-mcp speaks stdio and is what npx starts. todoist-mcp-http serves streamable HTTP, on 127.0.0.1:3000 unless told otherwise. Doist runs the same code as a hosted endpoint at https://ai.todoist.net/mcp with OAuth sign-in, and we list that endpoint as its own entry. Each tool is exported as a plain function too, for use in agent frameworks without MCP.

Count the entries in src/tool-registry.ts and you get 49 tools, a list missing from the README, which just points at the src/tools folder. Newest are get-user-status and set-user-status, for the status line beside your name in Todoist and Comms. Careful with the setter: it replaces the whole status, so any emoji or end time you leave out is dropped. It can pause Comms notifications, or Karma and streaks, while the status lasts.

search and fetch follow OpenAI's MCP format. There is a productivity-analysis prompt, plus an MCP Apps widget that draws find-tasks-by-date results as a task list in clients that support it. Every request to Todoist carries headers with the package version, a session id and the tool name (src/usage-tracking.ts). No setting in the stdio program turns this off.

What it needs

Node.js 24 or newer with npm 11 (package.json engines) for npx. A Todoist account and its personal API token, set as TODOIST_API_KEY. Running from source also needs git and npm to clone and build the repository.

Limits

• Limit The stdio program throws at start when TODOIST_API_KEY is unset, and every call runs as that one Todoist user (src/main.ts)
• Not covered No OAuth sign-in in the local package; OAuth is only offered on Doist's hosted endpoint
• Early release Its makers call the project early-stage and say the tools will change
• Limit The HTTP program refuses requests whose Host or Origin header is off its allowlist; binding beyond 127.0.0.1 needs HOST and ALLOWED_HOSTS together
• Limit The docs offer the local HTTP mode as a fallback when the hosted service drops sessions often

The stdio program exits at start with an error if TODOIST_API_KEY is not set, and it acts as that one Todoist user; there is no OAuth flow in the local package (OAuth is only on the hosted endpoint). Its makers call the project early-stage and say tools will change. The docs suggest the local HTTP mode as a fallback for frequent session disconnections on the hosted service. The HTTP program rejects requests whose Host or Origin header is not on its allowlist; binding to another interface needs HOST and ALLOWED_HOSTS set together.

Who it suits

Suits Todoist users who want an assistant to plan, file and tidy their tasks, and who prefer the vendor's own server, kept in step with the Todoist API, over a community one. Pick the local package when you want the token under your own control or the hosted endpoint drops sessions; pick Doist's hosted endpoint when you would rather sign in with OAuth than handle an API token. With delete, complete and bulk-update tools it can change a lot at once, so its makers suggest a test account or temporary project when trying write operations.