Todoist Python MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_projectsB | Get all todo projects. These are like folders for tasks in Todoist |
| get_tasksA | |
| delete_taskC | Delete a task by its ID |
| create_taskB | |
| update_taskB | |
| complete_taskC | Mark a task as done |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: complete_task marks tasks as done, create_task adds new tasks, delete_task removes tasks, get_projects retrieves projects, get_tasks fetches tasks with filtering, and update_task modifies existing tasks. The boundaries are well-defined and unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case: complete_task, create_task, delete_task, get_projects, get_tasks, update_task. This uniformity makes the tool set predictable and easy to understand at a glance.
With 6 tools, this server is well-scoped for a Todoist integration, covering core task management operations (create, read, update, delete, complete) and project listing. Each tool earns its place without being overwhelming or insufficient for the domain.
The tool set provides excellent coverage for task CRUD operations and project listing, enabling agents to manage tasks effectively. A minor gap exists in project management (e.g., no create_project or delete_project tools), but agents can still perform core workflows without significant hindrance.