Todoist MCP Server

An MCP (Model Context Protocol) server that connects Claude with Todoist for complete task and project management through natural language.

Installation

Claude Desktop (One-Click Install)

1. Download todoist-mcp.mcpb from the latest release
2. Double-click the file (or drag onto Claude Desktop)
3. Enter your Todoist API token when prompted
4. Start chatting: "Show me my Todoist projects"

Claude Code / Other MCP Clients

claude mcp add todoist -e TODOIST_API_TOKEN=your_token -- npx @greirson/mcp-todoist

{
  "mcpServers": {
    "todoist": {
      "command": "npx",
      "args": ["@greirson/mcp-todoist"],
      "env": {
        "TODOIST_API_TOKEN": "your_api_token_here"
      }
    }
  }
}

Features

• 19 MCP Tools for complete Todoist management
• Task Management: Create, update, delete, complete, reopen tasks with priorities, due dates, labels
• Bulk Operations: Process multiple tasks efficiently
• Subtasks: Hierarchical task management with completion tracking
• Projects & Sections: Full organization support
• Labels, Filters, Reminders: Pro/Business features supported
• Natural Language: Quick add with Todoist's natural language parsing
• Dry-Run Mode: Test operations without making changes

Dry-Run Mode

Dry-run mode allows you to test operations and automations without making any real changes to your Todoist workspace. This is perfect for testing, debugging, learning the API, or validating automation scripts before running them for real.

How to Enable Dry-Run Mode

Add DRYRUN=true to your environment configuration:

{
  "mcpServers": {
    "todoist": {
      "command": "npx",
      "args": ["@greirson/mcp-todoist"],
      "env": {
        "TODOIST_API_TOKEN": "your_api_token_here",
        "DRYRUN": "true"
      }
    }
  }
}

What Dry-Run Mode Does

• Validates Operations: Uses real API data to validate that operations would succeed
• Simulates Mutations: Create, update, delete, and complete operations are simulated (not executed)
• Real Data Queries: Read operations (get tasks, projects, labels) use the real API
• Detailed Logging: Shows exactly what would happen with clear [DRY-RUN] prefixes
• Error Detection: Catches the same errors that would occur in real execution

Use Cases

• Testing Automations: Validate complex bulk operations before executing
• Learning the API: Explore functionality without fear of making unwanted changes
• Debugging Issues: Understand what operations would be performed
• Safe Experimentation: Try new workflows without affecting your actual tasks
• Training and Demos: Show how operations work without modifying real data

Example Usage

With dry-run mode enabled, operations show what would happen:

You: "Create a task called 'Test Task' in my Work project"

Response:
[DRY-RUN] Dry-run mode enabled - mutations will be simulated
[DRY-RUN] Would create task: "Test Task" in project 2203306141, section none

Task created successfully (simulated):
ID: 100001
Title: Test Task
Project: Work (2203306141)
Priority: 4 (Normal)

Supported Operations

All 19 MCP tools support dry-run mode:

• Task creation, updates, completion, and deletion
• Subtask operations and hierarchy changes
• Bulk operations across multiple tasks
• Project and section creation
• Label management operations
• Reminder CRUD operations
• Comment creation

Dis

... View full README on GitHub