Todoist AI MCP Server

Official

by Doist

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

add-tasks

Add one or more tasks to a project, section, or parent task, and assign them to project collaborators.

Instructions

Add one or more tasks to a project, section, or parent. Supports assignment to project collaborators.

Input Schema

Name	Required	Description	Default
`tasks`	Yes	The array of tasks to add (max 25).

Output Schema

Name	Required	Description
`tasks`	Yes	The created tasks.
`failures`	Yes	Tasks that could not be created, with the reason for each.
`totalCount`	Yes	The total number of tasks created.
`failureCount`	Yes
`successCount`	Yes
`totalRequested`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv13.8.4Nov 2, 2026
- removedOutput schema / properties / tasks / items / properties / recurring / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "string"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / recurring / type
```
Added value: +[
+  "boolean",
+  "string"
+]
```

Changed4 schema fields changedv13.8.0Oct 29, 2026

removedOutput schema / properties / failureCount / description
```
Removed value: -"The number of failed task creations."
```

changedOutput schema / properties / failures / description

Previous value: -"Failed task creations with error details."New value: +"Tasks that could not be created, with the reason for each."

removedOutput schema / properties / successCount / description

Removed value: -"The number of successfully created tasks."

removedOutput schema / properties / totalRequested / description
```
Removed value: -"The total number of tasks requested."
```

Changed2 schema fields changedv13.3.0Sep 18, 2026

changedInput schema / properties / tasks / items / properties / duration / description

Previous value: -"The duration of the task. Use format: \"2h\" (hours), \"90m\" (minutes), \"2h30m\" (combined), or \"1.5h\" (decimal hours). Max 24h."New value: +"The duration of the task. Use format: \"2h\" (hours), \"90m\" (minutes), \"2h30m\" (combined), \"1.5h\" (decimal hours), or \"3d\" (whole days; days cannot be combined with hours or minutes). Todoist apps only display durations under 24 hours: a longer or day-based duration is stored and reported by this server, but the apps show the task as having no duration."

changedOutput schema / properties / tasks / items / properties / duration / description

Previous value: -"e.g. \"2h30m\"."New value: +"e.g. \"2h30m\", or \"3d\" for a day-based duration."

Changed1 schema field changedv13.2.7Sep 16, 2026
- addedOutput schema / properties / tasks / items / properties / isDeleted
```
Added value: +{
+  "description": "True when deleted; absent otherwise.",
+  "type": "boolean"
+}
```

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"

Changed21 schema fields changedv12.5.3Aug 7, 2026
- removedOutput schema / properties / failures / items / properties / code / description
```
Removed value: -"The error code, if available."
```
- removedOutput schema / properties / failures / items / properties / error / description
```
Removed value: -"The error message."
```
- changedOutput schema / properties / failures / items / properties / item / description
```
Previous value: -"The item that failed (usually an ID or identifier)."New value: +"Usually the ID of the item that failed."
```
- changedOutput schema / properties / tasks / items / properties / addedAt / description
```
Previous value: -"When the task was created (ISO 8601 format)."New value: +"ISO 8601."
```
- removedOutput schema / properties / tasks / items / properties / assignedByUid / description
```
Removed value: -"The UID of the user who assigned this task."
```
- changedOutput schema / properties / tasks / items / properties / checked / description
```
Previous value: -"Whether the task is checked/completed."New value: +"Whether the task is completed."
```
- changedOutput schema / properties / tasks / items / properties / completedAt / description
```
Previous value: -"When the task was completed (ISO 8601 format)."New value: +"ISO 8601."
```
- changedOutput schema / properties / tasks / items / properties / content / description
```
Previous value: -"The task title/content."New value: +"Task title."
```
- changedOutput schema / properties / tasks / items / properties / deadlineDate / description
```
Previous value: -"The deadline date of the task (ISO 8601 format)."New value: +"ISO 8601."
```
- removedOutput schema / properties / tasks / items / properties / description / description
```
Removed value: -"The task description."
```
- changedOutput schema / properties / tasks / items / properties / dueDate / description
```
Previous value: -"The due date of the task (ISO 8601 format)."New value: +"ISO 8601."
```
- changedOutput schema / properties / tasks / items / properties / duration / description
```
Previous value: -"The duration of the task (e.g., \"2h30m\")."New value: +"e.g. \"2h30m\"."
```
- removedOutput schema / properties / tasks / items / properties / id / description
```
Removed value: -"The unique ID of the task."
```
- changedOutput schema / properties / tasks / items / properties / isUncompletable / description
```
Previous value: -"Whether the task is uncompletable (organizational header)."New value: +"An organizational header, not a real task."
```
- removedOutput schema / properties / tasks / items / properties / labels / description
```
Removed value: -"The labels attached to this task."
```
- removedOutput schema / properties / tasks / items / properties / parentId / description
```
Removed value: -"The ID of the parent task (for subtasks)."
```
- changedOutput schema / properties / tasks / items / properties / priority / description
```
Previous value: -"The priority level: p1 (highest), p2 (high), p3 (medium), p4 (lowest)."New value: +"p1 is highest, p4 lowest."
```
- removedOutput schema / properties / tasks / items / properties / projectId / description
```
Removed value: -"The ID of the project this task belongs to."
```
- changedOutput schema / properties / tasks / items / properties / recurring / description
```
Previous value: -"Whether the task is recurring, or the recurrence string."New value: +"False when not recurring, otherwise the recurrence string."
```
- removedOutput schema / properties / tasks / items / properties / responsibleUid / description
```
Removed value: -"The UID of the user responsible for this task."
```
- removedOutput schema / properties / tasks / items / properties / sectionId / description
```
Removed value: -"The ID of the section this task belongs to."
```

Changed1 schema field changedv12.4.0Aug 4, 2026

changedInput schema / properties / tasks / items / properties / dueString / description

Previous value: -"The due date for the task, in natural language."New value: +"The due date for the task, in natural language. Also use natural language for recurrences; do not prefix it with \"recurring\"."

Changed1 schema field changedv10.5.0Jul 10, 2026
- addedOutput schema / properties / tasks / items / properties / addedAt
```
Added value: +{
+  "description": "When the task was created (ISO 8601 format).",
+  "type": "string"
+}
```
First observedv10.4.2Jul 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the mutation profile is covered. The description's only added claim, 'supports assignment to project collaborators', is already documented on the responsibleUser property, and it says nothing about batch partial-failure behavior or the collaborator-membership prerequisite beyond what the schema states.

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?

Two compact sentences with the verb and targets front-loaded, no filler. It is efficient but so terse that it barely engages with a fairly complex batch payload.

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 and full parameter documentation exist, so return values need not be explained. However, for a non-idempotent batch mutation this description omits the 25-task cap, duplicate-risk on retry, and what happens if only some tasks in the array fail – gaps that matter for correct invocation.

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 description coverage is 100% and the nested task properties are richly documented, so the baseline of 3 applies. The description adds only the vague 'one or more' framing and the container list, without any syntax, ordering, or required-field guidance beyond the schema.

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?

States a specific verb (add) and resource (tasks) plus the three target containers (project, section, parent), so an agent can distinguish it from update-tasks or add-sections. It stops short of explicitly naming the sibling it supersedes for modification.

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

Usage Guidelines3/5

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

The phrase 'Add one or more tasks to a project, section, or parent' implies the usage context (task creation, batch-capable), but it never states when to prefer this over update-tasks or when to use add-sections instead. Usage is inferable rather than explained.

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