Todoist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

import-project-template

Import a template into an existing project by adding its tasks, sections, and comments from a template ID, URL, or CSV export. This writes immediately without undo, so confirm the target project first.

Instructions

Import a template into an existing project, adding its tasks, sections and comments to whatever is already there. Source it by template ID/URL or by passing CSV content from export-project-template. To start a new project from a template, create the project with add-projects first, then import into it. This writes immediately and cannot be undone, so only run it against a project the user named.

Input Schema

TableJSON Schema

Name	Required	Description
`locale`	No	Locale for the imported content when using `templateId`. Defaults to "en".
`projectId`	Yes	The ID of the existing project to import the template into.
`templateId`	No	The template to import — either a gallery slug ("product-launch"), a personal template ID ("UT_28Ex..."), or a full Todoist template URL, which is reduced to the ID automatically. Gallery templates work for anyone; personal templates only for the account that owns them. There is no way to list templates through this server, so only use the ID or URL the user supplied. Provide either this or `csvFileContent`, not both.
`csvFileContent`	No	Raw CSV template content, as produced by export-project-template. Provide either this or `templateId`, not both.

Output Schema

TableJSON Schema

Name	Required	Description
`tasks`	Yes	Tasks created by the import.
`comments`	Yes	Comments created by the import.
`sections`	Yes	Sections created by the import.
`totalCount`	Yes	The total number of objects created by the import.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv13.3.0Sep 18, 2026
- 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"

Changed1 schema field changedv12.6.0Aug 19, 2026

addedOutput schema / properties / comments / items / properties / notifiedUserIds

Added value: +{
+  "description": "Users notified about this comment. Absent when nobody was notified.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed41 schema fields changedv12.5.3Aug 7, 2026
- removedOutput schema / properties / comments / items / properties / content / description
```
Removed value: -"The content of the comment."
```
- removedOutput schema / properties / comments / items / properties / fileAttachment / description
```
Removed value: -"File attachment information, if any."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileDuration / description
```
Previous value: -"The duration in milliseconds (for audio/video files)."New value: +"Milliseconds, for audio/video."
```
- removedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileName / description
```
Removed value: -"The name of the file."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileSize / description
```
Previous value: -"The size of the file in bytes."New value: +"Bytes."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileType / description
```
Previous value: -"The MIME type of the file."New value: +"MIME type."
```
- removedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileUrl / description
```
Removed value: -"The URL to access the file."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / image / description
```
Previous value: -"The image URL for image resource types."New value: +"For image resource types."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / imageHeight / description
```
Previous value: -"The height of the image in pixels."New value: +"Pixels."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / imageWidth / description
```
Previous value: -"The width of the image in pixels."New value: +"Pixels."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / resourceType / description
```
Previous value: -"The type of resource (file, url, image, etc)."New value: +"file, url, image, etc."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / title / description
```
Previous value: -"The title for link/url resource types."New value: +"For link/url resource types."
```
- removedOutput schema / properties / comments / items / properties / fileAttachment / properties / uploadState / description
```
Removed value: -"The upload state of the file."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / url / description
```
Previous value: -"The URL for link/url resource types."New value: +"For link/url resource types."
```
- removedOutput schema / properties / comments / items / properties / id / description
```
Removed value: -"The unique ID of the comment."
```
- changedOutput schema / properties / comments / items / properties / postedAt / description
```
Previous value: -"When the comment was posted (ISO 8601 format)."New value: +"ISO 8601."
```
- removedOutput schema / properties / comments / items / properties / postedUid / description
```
Removed value: -"The UID of the user who posted this comment."
```
- removedOutput schema / properties / comments / items / properties / projectId / description
```
Removed value: -"The ID of the project this comment belongs to."
```
- removedOutput schema / properties / comments / items / properties / taskId / description
```
Removed value: -"The ID of the task this comment belongs to."
```
- changedOutput schema / properties / sections / items / properties / description / description
```
Previous value: -"The description of the section. Supports Markdown."New value: +"Supports Markdown."
```
- removedOutput schema / properties / sections / items / properties / id / description
```
Removed value: -"The unique ID of the section."
```
- removedOutput schema / properties / sections / items / properties / name / description
```
Removed value: -"The name of the section."
```
- changedOutput schema / properties / sections / items / properties / sectionOrder / description
```
Previous value: -"The ordering index of the section within its project."New value: +"Ordering index within the project."
```
- 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."
```
Addedv12.5.0Aug 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds important non-obvious behavior beyond the annotations: writes immediately, cannot be undone, and merges into existing project content. It also clarifies template source limitations (gallery vs. personal templates). This does not contradict destructiveHint=false because the operation adds rather than destroys existing data, though it is irreversible.

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?

Three sentences, each earning its place: the primary behavior, the sourcing options, and the new-project workflow plus safety warning. The most important information is front-loaded before the cautionary guidance.

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

Completeness5/5

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

Provides the essential context for a mutating import operation: merge semantics, source options, workflow for new projects, and irreversibility. Since an output schema exists, the description doesn't need to explain return values, and nothing critical for correct invocation is missing.

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%, so the input schema already documents projectId, templateId, csvFileContent, and locale thoroughly. The description repeats the ID/URL/CSV distinction and the mutual exclusivity, but adds little meaning beyond what the schema already provides.

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?

States a specific verb ('import') with a clear resource (template) and target (existing project), and explains the merge semantics by listing what gets added: tasks, sections, and comments. It distinguishes itself from siblings like export-project-template and add-projects by focusing on importing into an existing project.

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

Usage Guidelines5/5

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

Explicitly names the workflow for new projects: create the project with add-projects first, then import. It also tells the agent when to use template ID/URL versus CSV content from export-project-template, and warns to only run it against a project the user named.

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