Todoist MCP Server

A local MCP server for Todoist task management, designed for use with Claude.

Wraps both the Todoist REST v2 and Sync API v1 to provide comprehensive task management capabilities through the Model Context Protocol.

Features

• Task CRUD — create, read, update, complete, delete, and move tasks

• Batch operations — update multiple tasks in a single API call via the Sync API

• Project management — list projects, resolve by name (case-insensitive)

• Labels — create, rename, delete, and apply labels to tasks

• Comments — read and add comments on tasks (Markdown supported)

• Completed tasks — query tasks completed within a date range (weekly review metrics)

• Graceful degradation — server starts without Todoist tools if API token is missing

Related MCP server: Todoist MCP

Setup

1. Get your Todoist API token

Go to Todoist Developer Settings and copy your API token.

2. Install

git clone https://github.com/stevesimpson418/todoist-mcp-server.git
cd todoist-mcp-server

# Install dependencies (creates .venv/ in the project directory)
uv sync

New to uv? uv sync reads pyproject.toml, creates a .venv/ virtualenv inside the project folder, and installs all dependencies into it. You don't need to activate it — uv run <command> handles that automatically.

3. Configure environment

cp .env.example .env
# Edit .env and add your TODOIST_API_TOKEN

4. Connect to Claude

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

Tip: Run uv run which python from the project directory to get the exact path for command.

{
  "mcpServers": {
    "todoist": {
      "command": "/absolute/path/to/todoist-mcp-server/.venv/bin/python",
      "args": ["-m", "todoist_mcp_server.server"],
      "env": {
        "TODOIST_API_TOKEN": "your_token_here"
      }
    }
  }
}

Adding to Claude Code CLI

Use the claude mcp add command to register the server. This works from any directory.

claude mcp add --scope user todoist-mcp-server \
  --transport stdio \
  --env TODOIST_API_TOKEN=your_token_here \
  -- /path/to/todoist-mcp-server/.venv/bin/python -m todoist_mcp_server.server

Replace /path/to/todoist-mcp-server with the actual path where you cloned the repo.

Tip: Run uv run which python from the project directory to get the exact .venv/bin/python path for the command.

The --scope user flag saves to ~/.claude.json so the server is available across all projects. Without it, the command defaults to local scope (tied to whatever directory you run it from). To scope it to a single project instead, use --scope project which writes to .mcp.json in the project root.

To verify the server is registered:

claude mcp list

Restart Claude Code after adding. The Todoist tools should appear in the /mcp menu.

Note: Claude Code CLI uses a different configuration from Claude Desktop. The claude mcp add command is the recommended way to register MCP servers — do not add them to ~/.claude/settings.json as that file is used for permissions and hooks only.

Updating

To pull the latest version and update dependencies:

cd /path/to/todoist-mcp-server
git pull
uv sync

Restart Claude Desktop or Claude Code CLI after updating.

Available tools

Usage Examples

Weekly review — see what you accomplished:

1. get_completed_tasks(since="2026-03-28", until="2026-04-04")  → completed this week
2. list_todoist_projects()                                       → see all projects
3. get_project_tasks(project_name="Inbox")                       → triage leftover inbox tasks

Reorganise tasks across projects:

1. get_project_tasks(project_name="Inbox")                          → find tasks to sort
2. move_task(task_id="123456", project_name="Home Renovation")      → move to the right project
3. batch_update_tasks(tasks=[
       {"id": "234567", "labels": ["waiting-on"]},
       {"id": "345678", "priority": 3}
   ])                                                               → bulk tidy-up

Quick capture with context:

1. create_task(
       content="Review pull request #42",
       project_name="Work",
       due_string="tomorrow 10am",
       priority=3
   )
2. add_task_comment(task_id="456789", content="See https://github.com/org/repo/pull/42")

Development

# Install dev dependencies
uv sync --dev

# Run tests
uv run pytest -v

# Run tests with coverage
uv run pytest --cov=todoist_mcp_server --cov-report=term-missing

# Lint
uv run ruff check src/ tests/

# Format
uv run ruff format src/ tests/

# Install git hooks
lefthook install

Local .env file

When running the server manually outside Claude Desktop/Code (e.g., for development or debugging), you can create a .env file in the project root so the server picks up the API token without passing environment variables:

TODOIST_API_TOKEN=your_token_here

This is only needed for local development. The Claude Desktop and Claude Code CLI configs pass this value directly via the env block.

Releases

This project uses release-please for automated versioning and releases. The version is determined by Conventional Commits:

• fix: commits bump the patch version (e.g. 0.1.0 → 0.1.1)

• feat: commits bump the minor version (e.g. 0.1.1 → 0.2.0)

• BREAKING CHANGE in the commit footer bumps the major version

When commits land on main, release-please opens (or updates) a Release PR that:

• Bumps the version in pyproject.toml

• Updates CHANGELOG.md with grouped entries

Merging the Release PR creates a git tag and GitHub Release automatically.

Packaging & Distribution

This server is currently distributed as source via git. To install:

git clone https://github.com/stevesimpson418/todoist-mcp-server.git
cd todoist-mcp-server
uv sync

This is the standard distribution model for local-stdio MCP servers today. The project is already configured for wheel builds via hatchling, so future distribution options include:

• PyPI — publish to PyPI, then install with uv tool install todoist-mcp-server or pip install todoist-mcp-server. Would require adding a publish workflow to CI.

• uvx — once on PyPI, uvx todoist-mcp-server runs the server without cloning the repo. Claude Desktop/Code config would point to the uvx-managed binary instead of a local .venv.

License

MIT