Skip to main content
Glama
dan-bailey

Todoist MCP Server

by dan-bailey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TODOIST_API_TOKENYesYour Todoist API token (required for authentication with Todoist API)

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_tasksC

Get tasks from Todoist with optional filtering.

Args:
    project_id: Filter tasks by project ID
    section_id: Filter tasks by section ID
    label: Filter tasks by label
    filter_query: Natural language filter (e.g., 'today', 'overdue', 'p1')
get_taskC

Get a specific task by ID.

Args:
    task_id: The ID of the task to retrieve
create_taskA

Create a new task in Todoist.

Args:
    content: The task content/title
    description: Detailed description of the task
    project_id: Project ID to add the task to
    section_id: Section ID within the project
    parent_id: Parent task ID (for subtasks)
    labels: List of label names
    priority: Priority from 1 (normal) to 4 (urgent)
    due_string: Human readable due date (e.g., 'tomorrow', 'next Monday')
    due_date: ISO 8601 formatted due date
update_taskB

Update an existing task.

Args:
    task_id: The ID of the task to update
    content: Updated task content/title
    description: Updated task description
    labels: Updated list of label names
    priority: Updated priority from 1 (normal) to 4 (urgent)
    due_string: Updated human readable due date
    due_date: Updated ISO 8601 formatted due date
complete_taskB

Mark a task as completed.

Args:
    task_id: The ID of the task to complete
reopen_taskC

Reopen a completed task.

Args:
    task_id: The ID of the task to reopen
delete_taskC

Delete a task.

Args:
    task_id: The ID of the task to delete
get_projectsB

Get all projects from Todoist.

get_projectA

Get a specific project by ID.

Args:
    project_id: The ID of the project to retrieve
create_projectB

Create a new project in Todoist.

Args:
    name: The name of the project
    parent_id: Parent project ID (for nested projects)
    color: Project color
    is_favorite: Whether to mark as favorite
get_sectionsC

Get sections from a project.

Args:
    project_id: Project ID to get sections from (optional)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 11 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific resources (tasks, projects, sections) and actions (create, get, update, delete, complete, reopen), making it easy for an agent to select the right tool. For example, 'complete_task' and 'reopen_task' handle task state changes, while 'update_task' handles content modifications.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern throughout, using snake_case. The verbs are clear and appropriate (e.g., create, get, update, delete, complete, reopen), and nouns specify the resource (e.g., task, project, sections). There are no deviations or mixed conventions.

Tool Count5/5

With 11 tools, this server is well-scoped for managing Todoist tasks and projects. Each tool earns its place by covering essential operations like CRUD for tasks and projects, plus specific actions like completing/reopening tasks and retrieving sections. The count is neither too thin nor excessive for the domain.

Completeness5/5

The tool surface provides complete CRUD/lifecycle coverage for tasks and projects, with no obvious gaps. It includes creation, retrieval, updating, and deletion for both resources, plus state management (complete/reopen) for tasks and section retrieval. This allows agents to handle all core workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources