Skip to main content
Glama
Johnxjp

Todoist Python MCP Server

by Johnxjp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
get_projectsB

Get all todo projects. These are like folders for tasks in Todoist

get_tasksA
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.
delete_taskC

Delete a task by its ID

create_taskB
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

Returns:
- task_id: str:
update_taskB
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.
complete_taskC

Mark a task as done

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues