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. You can find this in your Todoist settings under 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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tasksB | List tasks with optional filtering by project, label, priority, due date, or custom filter |
| get_taskB | Get detailed information about a specific task including comments and subtasks |
| create_taskC | Create a new task with optional due date, priority, labels, and project |
| update_taskC | Update an existing task (content, due date, priority, labels, etc.) |
| complete_taskA | Mark a task as complete. For recurring tasks, this completes the current occurrence. |
| uncomplete_taskC | Reopen a completed task |
| delete_taskC | Permanently delete a task |
| move_taskC | Move a task to a different project, section, or make it a subtask |
| list_projectsB | List all projects in the Todoist account |
| create_projectC | Create a new project |
| list_sectionsC | List sections within a project |
| create_sectionC | Create a new section within a project |
| update_projectC | Update an existing project (name, color, favorite status, view style) |
| delete_projectB | Permanently delete a project and all its tasks |
| update_sectionC | Update a section (rename or collapse/expand) |
| move_sectionC | Move a section to a different project |
| delete_sectionB | Permanently delete a section (tasks will be moved to project root) |
| list_labelsB | List all labels in the Todoist account |
| create_labelC | Create a new label |
| update_labelC | Update an existing label (name, color, favorite status, order) |
| delete_labelA | Permanently delete a label (tasks will keep their other labels) |
| add_commentC | Add a comment to a task |
| get_productivity_statsC | Get task completion statistics and productivity insights |
| quick_addA | Quickly add a task using natural language. Todoist will parse dates, priorities, labels, and projects from the text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_planning | Morning planning workflow to review and prioritize your day |
| weekly_review | GTD-style weekly review workflow |
| quick_capture | Rapidly capture multiple tasks or ideas |
| task_breakdown | Break down a large task into actionable subtasks |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| today | Today's tasks including overdue items |
| upcoming | Tasks due in the next 7 days |
| overdue | All overdue tasks requiring attention |
| projects | Project overview with task counts |
| labels | Available labels and usage counts |
TDQS
Scored across 24 tools
Every tool has a clearly distinct purpose targeting specific resources (tasks, projects, labels, sections) and actions (create, get, list, update, delete, move, complete). No ambiguity exists; for example, create_task vs. quick_add are differentiated by input method, and move_task vs. update_task handle different aspects of task modification.
All tools follow a consistent verb_noun pattern (e.g., create_task, list_labels, update_project) with no deviations. The naming is uniform and predictable, making it easy for agents to understand and select tools based on their actions and targets.
With 24 tools, the count is borderline high for a todo management server, potentially feeling heavy. While each tool serves a specific function, the number might overwhelm agents, as typical well-scoped servers have 3-15 tools. However, it's not extreme enough to score lower.
The tool set provides complete CRUD/lifecycle coverage for the Todoist domain, including tasks, projects, labels, and sections. It covers all essential operations from creation to deletion, with additional utilities like moving, commenting, and productivity stats, leaving no obvious gaps for agent workflows.