Todoist MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TODOIST_API_TOKEN | Yes | Your Todoist API token from Todoist Settings > Integrations > Developer |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| todoist_list_tasksC | List active tasks with optional filters (project, section, label, or Todoist filter query) |
| todoist_get_taskB | Get a single task by ID |
| todoist_create_taskB | Create a new task with optional due date, priority, labels, and project/section assignment |
| todoist_update_taskC | Update an existing task |
| todoist_complete_taskC | Mark a task as completed |
| todoist_reopen_taskC | Reopen a completed task |
| todoist_delete_taskC | Delete a task permanently |
| todoist_move_taskC | Move a task to a different project, section, or parent |
| todoist_create_tasks_batchC | Create multiple tasks at once (uses parallel API calls) |
| todoist_search_tasksB | Search for tasks by content using Todoist search filter |
| todoist_list_projectsB | List all projects |
| todoist_get_projectC | Get a project by ID |
| todoist_create_projectC | Create a new project |
| todoist_update_projectC | Update a project |
| todoist_delete_projectC | Delete a project permanently |
| todoist_list_sectionsB | List all sections (optionally filtered by project) |
| todoist_get_sectionC | Get a section by ID |
| todoist_create_sectionC | Create a new section in a project |
| todoist_update_sectionC | Update a section name |
| todoist_delete_sectionB | Delete a section |
| todoist_list_commentsC | List comments for a task or project |
| todoist_get_commentC | Get a comment by ID |
| todoist_create_commentC | Create a comment on a task or project with optional prefix tags |
| todoist_update_commentC | Update a comment |
| todoist_delete_commentC | Delete a comment |
| todoist_add_research_commentB | Add a research note to a task (prefixed with [Research]) |
| todoist_add_context_commentB | Add context information to a task (prefixed with [Context]) |
| todoist_list_completed_tasksC | List completed tasks (uses Sync API) with optional filters |
| todoist_get_completed_statsC | Get statistics about completed tasks |
| todoist_list_labelsB | List all personal labels |
| todoist_create_labelC | Create a new label |
| todoist_update_labelC | Update a label |
| todoist_delete_labelC | Delete a label |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Every tool has a clearly distinct purpose targeting specific resources (tasks, projects, sections, labels, comments) and actions (create, get, list, update, delete, complete, reopen, move, search). No ambiguity exists—for example, todoist_create_task, todoist_update_task, and todoist_complete_task are well-differentiated, and comment tools are specialized by prefix or general use.
All tools follow a consistent snake_case pattern with a 'todoist_' prefix and verb_noun structure (e.g., todoist_create_task, todoist_list_projects). Minor variations like 'todoist_add_context_comment' vs. 'todoist_create_comment' are semantically justified and maintain readability without breaking the pattern.
33 tools is excessive for a Todoist server, making the set feel heavy and potentially overwhelming. While it covers many operations, the count could be streamlined—for instance, batch operations or specialized comment tools might be consolidated without losing functionality, aligning better with typical MCP scopes of 3-15 tools.
The tool set provides complete CRUD/lifecycle coverage for all core Todoist entities (tasks, projects, sections, labels, comments), including advanced operations like moving tasks, reopening completed ones, searching, and batch creation. No obvious gaps exist; agents can perform any expected workflow without dead ends.