Todoist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

project-management

Idempotent

Archive, unarchive, or join Todoist projects by ID to manage project status and access unjoined workspace projects on a user's behalf.

Instructions

Archive or unarchive a project by its ID, or join a workspace project the user hasn't joined (see find-projects includeUnjoined) when they ask to.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "projectId": "<projectId>"
    },
    "name": "project-management"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes	The action to perform on the project.
`projectId`	Yes	The ID of the project.

Output Schema

Name	Required	Description	Default
`project`	Yes	The updated project.
`success`	Yes	Whether the action was successful.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv15.2.0Nov 12, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "archive",
-  "unarchive"
-]New value: +[
+  "archive",
+  "unarchive",
+  "join"
+]

Changed1 schema field changedv13.10.1Nov 5, 2026
- changedOutput schema / properties / project / properties / viewStyle / description
```
Previous value: -"list, board or calendar."New value: +"list, board, calendar or table."
```

Changed2 schema fields changedv13.0.0Aug 20, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed13 schema fields changedv12.5.3Aug 7, 2026
- changedOutput schema / properties / project / properties / childOrder / description
```
Previous value: -"The ordering index of the project among its siblings."New value: +"Ordering index among siblings."
```
- removedOutput schema / properties / project / properties / color / description
```
Removed value: -"The color key of the entity."
```
- changedOutput schema / properties / project / properties / description / description
```
Previous value: -"The description of the project (empty string if none)."New value: +"Empty string when none."
```
- changedOutput schema / properties / project / properties / folderId / description
```
Previous value: -"The ID of the folder this project belongs to (workspace projects only)."New value: +"Workspace projects only."
```
- removedOutput schema / properties / project / properties / id / description
```
Removed value: -"The unique ID of the project."
```
- removedOutput schema / properties / project / properties / inboxProject / description
```
Removed value: -"Whether this is the inbox project."
```
- removedOutput schema / properties / project / properties / isArchived / description
```
Removed value: -"Whether the project is archived."
```
- removedOutput schema / properties / project / properties / isFavorite / description
```
Removed value: -"Whether the project is marked as favorite."
```
- removedOutput schema / properties / project / properties / isShared / description
```
Removed value: -"Whether the project is shared."
```
- removedOutput schema / properties / project / properties / name / description
```
Removed value: -"The name of the project."
```
- removedOutput schema / properties / project / properties / parentId / description
```
Removed value: -"The ID of the parent project (for sub-projects)."
```
- changedOutput schema / properties / project / properties / viewStyle / description
```
Previous value: -"The view style of the project (list, board, calendar)."New value: +"list, board or calendar."
```
- changedOutput schema / properties / project / properties / workspaceId / description
```
Previous value: -"The ID of the workspace this project belongs to (undefined for personal projects)."New value: +"Undefined for personal projects."
```
First observedv10.4.2Jul 9, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the safety profile (not read-only, non-destructive, idempotent), so the bar is lower. The description adds the useful implicit point that archiving is reversible because unarchive exists, but it never states what archiving does to child tasks/sections or whether joining a workspace project requires workspace permissions. With annotations carrying safety, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, and the three actions appear before the qualifying parenthetical. The nested '(see find-projects includeUnjoined)' and trailing 'when they ask to' make the sentence harder to parse than it needs to be, costing a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover safety and idempotency, so return format and safety needn't be restated. What is missing is behavior around side effects of archive on contained tasks/sections and any permission prerequisite for joining a workspace project, which are material for a mutation tool with a three-way action enum.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters carry inline descriptions, so the baseline is 3. The description adds only modest meaning beyond the schema: it clarifies that projectId targets a project and that the join action presupposes an unjoined project. No format, ID-source, or edge-case detail is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete verbs (archive, unarchive, join) and the resource (project keyed by ID), which is well beyond a tautology. It also distinguishes the join case from lookup-style siblings by pointing at find-projects' includeUnjoined option. The only reason it isn't a 5 is the tangled final clause ('when they ask to') that slightly muddies the scope statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear precondition for the join action (the user hasn't joined that workspace project yet) and routes the agent to find-projects/includeUnjoined to determine that state. It does not spell out when-not cases, such as attempting to join a project already joined, nor whether archive should be preferred over other mutation tools, so it stops short of explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.