Todoist AI MCP Server

Official

by Doist

Overview Schema Related Servers Score Discussions

TypeScript

Remote

add-comments

Add comments to tasks or projects in Todoist, with optional user notifications.

Instructions

Add multiple comments to tasks or projects, optionally notifying collaborators. Each comment must specify either taskId or projectId.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`comments`	Yes	The array of comments to add.

Output Schema

TableJSON Schema

Name	Required	Description
`comments`	Yes	The created comments.
`totalCount`	Yes	The total number of comments created.
`addedCommentIds`	Yes	The IDs of the added comments.

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"

Changed2 schema fields changedv12.6.0Aug 19, 2026

addedInput schema / properties / comments / items / properties / notifyUsers

Added value: +{
+  "description": "Who to notify about this comment — a user ID, email, full name, or \"me\" for each person. Set this whenever the comment mentions someone; the text of an @mention notifies nobody on its own. Omit to notify whoever the Todoist apps would (the task's assignee, assigner and creator on a first comment, or the previous comment's participants on a reply). Pass [\"none\"] to notify nobody.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 25,
+  "minItems": 1,
+  "type": "array"
+}

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"
+}

Changed19 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."
```
First observedv10.4.2Jul 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description discloses that the tool modifies data (adds comments) and optionally notifies collaborators, which is behavioral information beyond the annotation (readOnlyHint false) and adds context. It does not mention potential side effects like activity logging, but the annotation already implies mutation, and the description covers the main behavior.

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?

The description is concise, consisting of two clear sentences. It avoids redundancy and conveys the essential information efficiently.

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?

The description does not mention what the tool returns (no output schema is provided) or any error conditions. While it covers the main functionality, the lack of return value information and potential pitfalls leaves some gaps, but it is adequate for a simple add operation.

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

Parameters4/5

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

The description adds a critical constraint that each comment must specify either taskId or projectId, which is not enforced by the schema. Other parameters like content and notifyUsers are already fully described in the schema, so the description focuses on the key requirement.

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?

The description clearly states the action (add multiple comments), the target (tasks or projects), and the optional notification behavior. It distinguishes from sibling tools like update-comments and find-comments by explicitly using 'add' and mentioning multiple comments.

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 provides clear context about what the tool does and the constraint that each comment must specify either taskId or projectId. However, it does not explicitly mention when to use this tool versus alternatives like update-comments or find-comments, but the intent is implied by the action verb.

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