complete_task
Mark a task as done
LABSCO SUMMARY
Tasks are fetched with their ids because every write needs one.
The shape of the tool set tells you how to use it: get_tasks returns ids, and update, complete and delete all take an id. So the working pattern is find-then-act — describe the task in words, let the listing tool resolve it, then operate on what came back. Dates take a plain YYYY-MM-DD, with deadline kept separate from due date.
What it is
A Python server over the Todoist API, covering task creation, retrieval and management. It handles the authentication and the data shaping so the conversation stays in terms of tasks rather than API payloads.
What you get
- A task created from its content, optionally with description, due date, priority, project, section and labels —
create_task - Tasks listed with ids and filters for project name or id, task name, priority, labels, overdue status and a limit —
get_tasks - An existing task updated by id: content, description, labels, priority,
due_dateanddeadline_date—update_task - A task completed or removed by id —
complete_task,delete_task
Requirements
A Todoist account and its API token in TODOIST_API_TOKEN, taken from User Settings → Integrations → Developer. Python 3.12 or later, and uv. Runs straight from the repository with uvx --from https://github.com/Johnxjp/todoist-mcp-python.git mcp-server-todoist, so there is nothing to clone first.
Setup effort
One command plus a key — uvx --from https://github.com/Johnxjp/todoist-mcp-python.git mcp-server-todoist, then supply credentials
USE CASES
01
Capturing a task the moment it comes up
Create it with content, a due date and the project it belongs in, rather than switching apps and losing the thread of what you were doing.
02
Seeing what is actually overdue
List tasks with the overdue filter and a priority filter, so you get the short list instead of the whole inbox.
03
Closing out work as you finish it
Find the task by name to get its id, then mark it complete — two calls, no app switch.
04
Re-prioritising after plans change
Pull the affected tasks, then update their priority, due date or deadline in place.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_task
Create a new task
Args:
- content [str]: Task content. This value may contain markdown-formatted text and hyperlinks. Details on markdown support can be found in the Text Formatting article in the Help Center.
- description [str]: A description for the task. This value may contain markdown-formatted text and hyperlinks. Details on markdown support can be found in the Text Formatting article in the Help Center.
- project_id [str]: The ID of the project to add the task. If none, adds to user's inbox by default.
- labels [list[str]]: The task's labels (a list of names that may represent either personal or shared labels).
- priority [int]: Task priority from 1 (normal) to 4 (urgent).
- due_date [str]: Specific date in YYYY-MM-DD format relative to user’s timezone.
- section_id [str]: The ID of the section to add the task to
delete_task
Delete a task by its ID
get_projects
Get all todo projects. These are like folders for tasks in Todoist
get_tasks
Fetch user's tasks. These can be filtered by project, labels, time, etc. If no filters are provided, all tasks are returned.
Args:
- project_id: The string ID of the project to fetch tasks from. Example '1234567890'
- project_name: Name of the project to fetch tasks from. Example 'Work' or 'Inbox'
- task_name: Filter tasks by name. Example 'Buy groceries'
- labels: List of tags used to filter tasks.
- priority: Filter tasks by priority level. 4 (urgent), 3 (high), 2 (normal), 1 (low)
- due_date: Specific due date in YYYY-MM-DD format. Example '2021-12-31'
- is_overdue: Filter tasks that are overdue.
- limit: Maximum number of tasks to return. Default is all.
update_task
Update an attribute of a task given its ID. Any attribute can be updated.
Args:
- task_id [str | int]: The ID of the task to update. Example '1234567890' or 1234567890
- content [str]: Task content. This value may contain markdown-formatted text and hyperlinks. Details on markdown support can be found in the Text Formatting article in the Help Center.
- description [str]: A description for the task. This value may contain markdown-formatted text and hyperlinks. Details on markdown support can be found in the Text Formatting article in the Help Center.
- labels [list[str]]: The task's labels (a list of names that may represent either personal or shared labels).
- priority [int]: Task priority from 1 (normal) to 4 (urgent).
- due_date [str]: Specific date in YYYY-MM-DD format relative to user’s timezone.
- deadline_date [str]: Specific date in YYYY-MM-DD format relative to user’s timezone.
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected.
Requires
- Python 3.12 or later
- uv (it provides the uvx command the configuration runs)
- TODOIST_API_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx --from https://github.com/Johnxjp/todoist-mcp-python.git mcp-server-todoistMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"todoist-server": {
"command": "uvx",
"args": [
"--from",
"https://github.com/Johnxjp/todoist-mcp-python.git",
"mcp-server-todoist"
],
"env": {
"TODOIST_API_TOKEN": "<YOUR_TODOIST_API_TOKEN>"
}
}
}
}
