Todoist AI MCP Server

Official

Overview Schema Related Servers Score Discussions

add-tasks

Add tasks to Todoist projects, sections, or parent tasks with due dates, labels, priorities, durations, descriptions, and assignees. Supports up to 25 tasks per call, including subtasks and collaborator assignments.

Instructions

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

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`tasks`	Yes	The created tasks.
`failures`	Yes	Failed task creations with error details.
`totalCount`	Yes	The total number of tasks created.
`failureCount`	Yes	The number of failed task creations.
`successCount`	Yes	The number of successfully created tasks.
`totalRequested`	Yes	The total number of tasks requested.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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

A4.2/5.0

Behavior4/5

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

Annotations confirm non-read-only, non-idempotent, non-destructive behavior, and the description adds context by noting collaborator assignment and the ability to add to multiple locations. This complements the structured fields meaningfully.

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

Conciseness5/5

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

Two concise, front-loaded sentences with no redundancy. Every word adds value, specifying both action and key capability.

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

Completeness4/5

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

For a complex tool with a rich schema and existing output schema, the description covers the essential use case without over-explaining. It could mention batch limits (already in schema) but overall is sufficiently complete for an add-operation tool.

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% with comprehensive per-field descriptions. The tool description offers minimal additional semantic value beyond the schema, only hinting at project/section/parent through the description, which is already encoded in the schema properties.

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

Purpose5/5

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

Description uses a specific verb+resource combination: 'Add one or more tasks to a project, section, or parent.' It clearly defines the action and scope, and mentions a distinguishing capability ('Supports assignment to project collaborators').

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?

The description implies when to use it (adding tasks) and references destinations (project, section, parent) that suggest scope, but it does not explicitly mention alternatives or when not to use it. Clear context without exclusions.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Doist/todoist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server