Skip to main content
Glama
mehularora8

Todoist MCP Server

by mehularora8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TODOIST_API_TOKENYesYour Todoist API token, found in the Todoist Integrations Settings.

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_taskA
Create a new task in Todoist.

Priorities don't map directly to Todoist priorities, but are mapped as follows:
1 = low
2 = medium
3 = high
4 = urgent

This is done to map better to how people think about priorities.

Args:
    content: The task content/title (required)
    description: Task description (optional)
    project_name: Project name to add task to
    due_string: Due date in natural language like "tomorrow", "next monday" (optional)
    priority: Priority level 1-4 (1=low, 2=medium, 3=high, 4=urgent)
    labels: List of label names to add to the task (optional)

Returns:
    Dict containing the created task details or error message
list_active_tasksB
List tasks from Todoist

Args:
    project_name: Filter tasks by project name (alternative to project_id)
    filter_string: Todoist filter string like "today", "overdue", "p1" (optional)
    limit: Maximum number of tasks to return (default 50)

Returns:
    Dict containing list of tasks or error message
list_completed_tasksA
List completed tasks from Todoist within a timespan. Default is last 24 hours.
Prefer not to provide `since` and `until` if you want to pull tasks from the last 24 hours.

Args:
    project_name: Filter tasks by project name (optional)
    since: Start date in ISO format (YYYY-MM-DD) in the user's timezone (optional)
    until: End date in ISO format (YYYY-MM-DD) in the user's timezone (optional)
    limit: Maximum number of tasks to return (default 30, max 200)

Returns:
    Dict containing list of completed tasks or error message

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: create_task for creating new tasks, list_active_tasks for retrieving current tasks, and list_completed_tasks for viewing past tasks. There is no overlap in functionality, making it easy for an agent to select the right tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (create_task, list_active_tasks, list_completed_tasks) with clear and descriptive naming. There are no deviations in style or convention.

Tool Count2/5

With only 3 tools, the set feels too thin for a comprehensive Todoist integration. Key operations like updating tasks, deleting tasks, managing projects, or marking tasks as complete are missing, limiting the server's utility for full task management workflows.

Completeness2/5

The tool set is severely incomplete for a Todoist server. While it covers creation and listing (active and completed), it lacks essential CRUD operations such as update_task, delete_task, and complete_task, as well as project and label management tools, creating significant gaps that will hinder agent performance.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources