Todoist

You can manage Todoist tasks from an MCP client by running a Todoist MCP Server that exposes tasks, projects, labels, and prompts through MCP endpoints. This setup lets AI assistants create, organize, and track work in Todoist using natural language, while respecting Todoist’s structure and permissions.

How to use

Connect your MCP client to the Todoist MCP Server using a stdio-based integration. You provide your Todoist API token, and then your client can issue natural language tasks, list tasks, update items, and run planning prompts. Common workflows include creating tasks with natural due dates, viewing today’s tasks, and performing daily planning or quick capture.

Key capabilities you can access through the MCP endpoints include listing, creating, updating, completing, and deleting tasks; managing projects, sections, and labels; adding comments; retrieving productivity stats; and using resource links for quick task views. You can also invoke prompts like daily planning, weekly review, quick capture, and task breakdown to streamline your workflow.

How to install

Prerequisites: ensure you have Node.js installed on your machine and a Todoist API token ready.

1. Install dependencies for the Todoist MCP Server.

cd todoist-mcp
npm install

2. Build the server for production or distribution.

npm run build

3. Run the server in development mode to test locally.

npm run dev

4. Add the server to your Claude Code configuration using a stdio transport. Provide your Todoist API token in the environment and point to the compiled index script.

"mcpServers": {
  "todoist": {
    "command": "node",
    "args": ["/path/to/todoist-mcp/dist/index.js"],
    "env": {
      "TODOIST_API_TOKEN": "your_token_here"
    }
  }
}

Additional content

Configuration and usage options are designed to be straightforward. You supply the Todoist API token and run the MCP server locally, then connect to it from your MCP client. The server defaults respect Todoist’s rate limits and include caching for projects and labels to improve responsiveness.

Environment variables you typically need to set include the Todoist API token. The following example shows how to start the server in a typical setup.

claude mcp add --transport stdio todoist \
  --env TODOIST_API_TOKEN=your_token_here \
  -- node /path/to/todoist-mcp/dist/index.js

Available tools

list_tasks

List tasks with filtering by project, priority, due date, and more.

get_task

Get detailed information about a task, including comments and subtasks.

create_task

Create tasks with natural language due dates and optional attributes.

update_task

Update a task's content, due date, priority, labels, and more.

complete_task

Mark tasks as complete, including handling of recurring tasks.

uncomplete_task

Reopen tasks that were previously completed.

delete_task

Permanently delete tasks.

move_task

Move tasks between projects or sections.

list_projects

List all projects.

create_project

Create new projects.

update_project

Update project attributes like name, color, and view style.

delete_project

Permanently delete projects.

list_sections

List sections within projects.

create_section

Create new sections.

update_section

Rename or collapse/expand sections.

move_section

Move sections between projects.

delete_section

Permanently delete sections.

list_labels

List all labels.

create_label

Create new labels.

update_label

Update label name, color, or order.

delete_label

Permanently delete labels.

add_comment

Add comments to tasks.

get_productivity_stats

Get completion and productivity statistics.

quick_add

Add tasks using natural language entry.