todoist-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Todoist API token from Settings → Integrations under "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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_comments_listC | Get comments list from Todoist |
| create_commentsC | Create new comments in Todoist |
| get_commentsC | Get comments from Todoist by ID |
| update_commentsC | Update comments in Todoist |
| delete_commentsC | Delete comments in Todoist |
| get_labels_listB | Get all personal labels from Todoist |
| create_labelsC | Create a new personal labels in Todoist |
| get_labelsC | Get a personal label from Todoist Either 'id' or the 'name' to identify the target. |
| update_labelsC | Update a personal label in Todoist |
| delete_labelsC | Delete a personal label in Todoist Either 'id' or the 'name' to identify the target. |
| get_shared_labelsB | Get all shared labels from Todoist |
| rename_shared_labelsC | Rename a shared label in Todoist |
| remove_shared_labelsC | Remove a shared label in Todoist |
| get_projects_listB | Get all projects from Todoist |
| create_projectsC | Create new projects in Todoist |
| get_projectsC | Get projects from Todoist Either 'id' or the 'name' to identify the target. |
| update_projectsC | Update projects in Todoist Either 'id' or the 'name' to identify the target. |
| delete_projectsB | Delete projects from Todoist Either 'id' or the 'name' to identify the target. |
| get_collaboratorsC | Get all collaborators for a project in Todoist |
| move_projectsC | Move a projects to a different parent in Todoist |
| get_sections_listC | Get sections list from Todoist |
| create_sectionsC | Create new sections in Todoist |
| get_sectionsC | Get sections from Todoist Either 'id' or the 'name' to identify the target. |
| update_sectionsC | Update sections in Todoist |
| delete_sectionsC | Delete sections in Todoist Either 'id' or the 'name' to identify the target. |
| get_tasks_listC | Get tasks list from Todoist |
| create_tasksC | Create new tasks in Todoist |
| get_tasksC | Get tasks from Todoist Either 'task_id' or the 'task_name' to identify the target. |
| update_tasksC | Update tasks in Todoist Either 'task_id' or the 'task_name' to identify the target. |
| close_tasksC | Close tasks in Todoist Either 'task_id' or the 'task_name' to identify the target. |
| reopen_tasksC | Reopen tasks in Todoist Either 'task_id' or the 'task_name' to identify the target. |
| delete_tasksC | Delete tasks from Todoist Either 'task_id' or the 'task_name' to identify the target. |
| move_tasksB | Move tasks to a different parent or section in Todoist. Exactly one of parent_id, section_id, or project_id must be provided |
| get_completed_tasksC | Get completed tasks from Todoist with filtering options |
| utils_get_colorsB | Get available colors for projects, labels, filters in Todoist |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| projects_list |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 35 tools
Most tools have distinct purposes targeting specific resources (tasks, projects, labels, comments, sections) with clear CRUD operations, but there is some ambiguity between get_* and get_*_list pairs (e.g., get_comments vs get_comments_list) where the distinction might not be immediately clear without deeper inspection of parameters.
Tool names follow a highly consistent verb_noun pattern throughout (e.g., create_tasks, delete_projects, update_labels), with all tools using snake_case and predictable verbs (create, get, update, delete, close, reopen, move, remove, rename). The only minor deviation is utils_get_colors, but it still fits the overall pattern.
With 35 tools, the count is high for a Todoist integration, which typically involves core entities like tasks, projects, and labels. This feels borderline heavy as it includes many list vs. single-item get operations and specialized tools like move_projects or utils_get_colors, which might be overkill for basic agent workflows.
The tool set provides comprehensive CRUD and lifecycle coverage for all major Todoist entities (tasks, projects, labels, comments, sections), including advanced operations like moving tasks/projects, reopening tasks, and managing shared labels. There are no obvious gaps for typical agent interactions with the Todoist API.