The Todoist MCP server connects an agent to your tasks, projects and labels. Todoist’s strength has always been fast capture, and an agent that is already in the conversation where a commitment gets made is about as fast as capture gets.
What it actually does
Todoist’s official server, from Doist, runs as a hosted endpoint with OAuth, and can also run locally with an API token. It exposes Todoist’s model as tools. The agent can create tasks with due dates, priorities, labels and project assignment, complete existing ones, and read projects and filters. Because Todoist parses natural-language dates itself, the agent can pass “next Friday” straight through instead of doing calendar arithmetic.
Practical patterns:
- ‘Turn every action point from these notes into tasks in my Work project.’
- ‘What is due this week, and which of it has slipped from last week?’
- ‘Add a task to follow up on this, next Tuesday, with the thread summary in the description.‘
Why use it
The gap between deciding something needs doing and recording it is where tasks are lost. Doing it from the conversation closes that gap, and the tasks an agent creates carry better context than the three words you would have typed, because it has just read the thing that prompted them.
Gotchas
Duplicates are the common annoyance: an agent asked twice about the same notes will cheerfully create two sets. Tell it to check first. If you use a local API token, it grants full account access, so keep it out of anything shared. It is also worth installing the Time server alongside this one, because relative dates depend on the agent knowing what today actually is, and without a clock it does not.
