get_projectsLABSCO SUMMARY
Capture and planning in the same conversation.
The gap this closes is the one between deciding what to do and writing it down somewhere it will be seen. Because filters are supported as well as plain listing, 'what is overdue and unlabelled' is answerable — which is what makes it a planning tool rather than an inbox.
What it is
A full connection to your Todoist workspace. Projects, sections, tasks, labels and comments are each readable and writable, so planning a week and recording it are the same conversation.
What you get
- Projects listed, read, created, renamed and deleted
- Sections within a project, for structure below the project level
- Tasks created, updated, closed and deleted, including retrieval by Todoist's own filter syntax
- Labels, for the cross-project views Todoist is built around
- Comments, so the discussion stays attached to the task
- A published container image, so the client launches it without a local build
Requirements
A Todoist API token from your developer settings, and Docker — the documented configuration runs the published image with the token in its environment.
Setup effort
Run a container — pull the image and point your client at it
USE CASES
01
Setting up a project you just agreed to
Create the project and check it against what already exists, so the structure appears in Todoist while the plan is still fresh.
02
Renaming or reorganizing what you already have
Read the project, change what needs changing, and leave the rest alone — the small maintenance that otherwise never happens.
03
Clearing out projects that are finished
List what is there, delete the ones that are done, and confirm what is left — a periodic tidy done in one exchange.
04
Turning a conversation into tasks
Capture the actions from a discussion as tasks in the right project, with labels and comments attached, instead of retyping them later.
05
Working out what actually needs doing today
Query with Todoist's own filter syntax rather than reading a list — overdue, labelled, in one project — and close things off as you go.
32 tools
Listed in project docs. Your client may show a different list.
get_projectcreate_projectupdate_projectdelete_projectget_sectionsget_sectioncreate_sectionupdate_sectiondelete_sectionget_tasksget_tasks_by_filterget_taskcreate_taskupdate_taskdelete_taskclose_taskreopen_taskmove_tasks_to_projectmove_tasks_to_sectionmove_tasks_to_parentcreate_labelupdate_labelget_labelget_labelsdelete_labelcreate_task_commentcreate_project_commentupdate_commentget_task_commentsget_project_commentsdelete_commentBEFORE YOU INSTALL
What to know first
Tools you get
32 tools named in the project's documentation. delete_project and delete_label are irreversible, and update_section can change only the section name.
Requires
- Docker — the block runs the published image ghcr.io/koki-develop/todoist-mcp-server:latest
- A Todoist API token from Todoist Developer Settings, written into the block in place of <your_api_token_here>
- TODOIST_API_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Pull the image and point your client at it.
Server setup
Go to Todoist Developer Settings (https://app.todoist.com/app/settings/integrations/developer) and copy your API token
Add the mcpServers configuration to your MCP client; <YOUR_TODOIST_API_TOKEN> is that token — the docker image ghcr.io/koki-develop/todoist-mcp-server:latest is pulled automatically on first run
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"todoist": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TODOIST_API_TOKEN=<YOUR_TODOIST_API_TOKEN>",
"ghcr.io/koki-develop/todoist-mcp-server:latest"
]
}
}
}
