What can you do with this server?

The Todoist MCP Server integrates Claude with Todoist to enable natural language task management. With this server, you can: * Create tasks: Add new tasks with content, description, due dates, and priority levels * Retrieve tasks: Filter tasks by due date, priority, or project using natural language * Update tasks: Modify existing task attributes by searching for them by name * Complete tasks: Mark tasks as complete using natural language search * Delete tasks: Remove tasks by searching for them by name

Which integrations are available for this server?

Enables natural language task management in Todoist, allowing users to create, retrieve, update, complete, and delete tasks with support for task attributes like descriptions, due dates, and priority levels.

How do I use Todoist MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Todoist MCP Server Add a high priority task 'Finish quarterly report' due tomorrow" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

en es ja ko zh

Todoist MCP Server

by abhiz123

Overview Schema Related Servers Score Discussions

JavaScript

Remote

Todoist MCP Server

An MCP (Model Context Protocol) server implementation that integrates Claude with Todoist, enabling natural language task management. This server allows Claude to interact with your Todoist tasks using everyday language.

Features

Natural Language Task Management: Create, update, complete, and delete tasks using everyday language
Smart Task Search: Find tasks using partial name matches
Flexible Filtering: Filter tasks by due date, priority, and other attributes
Rich Task Details: Support for descriptions, due dates, and priority levels
Intuitive Error Handling: Clear feedback for better user experience

Related MCP server: Enhanced Todoist MCP Server Extended

Installation

Installing via Smithery

To install Todoist MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @abhiz123/todoist-mcp-server --client claude

Manual Installation

npm install -g @abhiz123/todoist-mcp-server

Tools

todoist_create_task

Create new tasks with various attributes:

Required: content (task title)
Optional: description, due date, priority level (1-4)
Example: "Create task 'Team Meeting' with description 'Weekly sync' due tomorrow"

todoist_get_tasks

Retrieve and filter tasks:

Filter by due date, priority, or project
Natural language date filtering
Optional result limit
Example: "Show high priority tasks due this week"

todoist_update_task

Update existing tasks using natural language search:

Find tasks by partial name match
Update any task attribute (content, description, due date, priority)
Example: "Update meeting task to be due next Monday"

todoist_complete_task

Mark tasks as complete using natural language search:

Find tasks by partial name match
Confirm completion status
Example: "Mark the documentation task as complete"

todoist_delete_task

Remove tasks using natural language search:

Find and delete tasks by name
Confirmation messages
Example: "Delete the PR review task"

Setup

Getting a Todoist API Token

Log in to your Todoist account
Navigate to Settings → Integrations
Find your API token under "Developer"

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "todoist": {
      "command": "npx",
      "args": ["-y", "@abhiz123/todoist-mcp-server"],
      "env": {
        "TODOIST_API_TOKEN": "your_api_token_here"
      }
    }
  }
}

Example Usage

Creating Tasks

"Create task 'Team Meeting'"
"Add task 'Review PR' due tomorrow at 2pm"
"Create high priority task 'Fix bug' with description 'Critical performance issue'"

Getting Tasks

"Show all my tasks"
"List tasks due today"
"Get high priority tasks"
"Show tasks due this week"

Updating Tasks

"Update documentation task to be due next week"
"Change priority of bug fix task to urgent"
"Add description to team meeting task"

Completing Tasks

"Mark the PR review task as complete"
"Complete the documentation task"

Deleting Tasks

"Delete the PR review task"
"Remove meeting prep task"

Development

Building from source

# Clone the repository
git clone https://github.com/abhiz123/todoist-mcp-server.git

# Navigate to directory
cd todoist-mcp-server

# Install dependencies
npm install

# Build the project
npm run build

Contributing

Contributions are welcome! Feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Issues and Support

If you encounter any issues or need support, please file an issue on the GitHub repository.

Available Tools

5 tools

todoist_complete_taskB

Mark a task as complete by searching for it by name

ParametersJSON Schema

Name	Required	Description	Default
`task_name`	Yes	Name/content of the task to search for and complete

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It mentions it searches by name and marks complete, but omits important details: what happens if no task is found, if multiple tasks match, whether the action is reversible, or any authentication/permission requirements. The mutation and side effects are under-described.

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?

The description is a single sentence that concisely conveys the purpose. It is front-loaded with the verb 'Mark'. However, it could be slightly more structured by separating the searching and completion steps.

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?

Given the simplicity of the tool (one param, no output schema, no nested objects), the description is adequate for understanding the core functionality. It does not explain return values, but that is acceptable without an output schema.

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?

The input schema has 100% description coverage for the single parameter 'task_name'. The description adds 'search for and complete' which is already implied by the schema description. No additional semantic meaning 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?

The description clearly states the action: 'Mark a task as complete', specifying the resource (task) and the operation (complete). It distinguishes from sibling tools like create, delete, get, update by focusing on completion, but the phrase 'searching for it by name' adds a minor nuance that could imply searching behavior beyond completion.

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 description implies when to use the tool (when you want to complete a task by name) but does not provide explicit guidance on when not to use it or mention alternatives. For example, it doesn't clarify if this is preferred over updating the task's status via 'todoist_update_task'.

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

todoist_create_taskB

Create a new task in Todoist with optional description, due date, and priority

ParametersJSON Schema

Name	Required	Description
`content`	Yes	The content/title of the task
`priority`	No	Task priority from 1 (normal) to 4 (urgent) (optional)
`due_string`	No	Natural language due date like 'tomorrow', 'next Monday', 'Jan 23' (optional)
`description`	No	Detailed description of the task (optional)

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It lacks disclosure of side effects, return values, or error conditions. Only states basic creation with optional fields.

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?

Single sentence, 15 words, no redundancy. Core action and resource are front-loaded. Every word adds value, and the structure is efficient.

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

Completeness2/5

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

Given the complexity (4 parameters, no output schema, no annotations), the description lacks completeness. It does not mention what the tool returns on success, error handling, or prerequisites for use.

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 baseline is 3. The description adds minimal value by restating that fields are optional, which is already clear from the schema. No additional semantics beyond what the schema 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?

The description clearly specifies the action 'Create' and the resource 'task in Todoist', and lists optional fields. It distinguishes the tool from siblings like update, delete, complete, and get by focusing on creation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No prerequisites or context provided, leaving the agent to infer based solely on the tool name and sibling list.

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

todoist_delete_taskB

Delete a task from Todoist by searching for it by name

ParametersJSON Schema

Name	Required	Description	Default
`task_name`	Yes	Name/content of the task to search for and delete

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavior. It states the tool searches by name and deletes, but fails to clarify behavior for ambiguous names (e.g., multiple matches), required authentication, side effects, or success/failure responses.

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?

The description is a single, clear sentence with no unnecessary words. It is efficient, though it could be slightly more precise by specifying what happens with multiple matches or the return type.

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?

For a simple one-parameter delete tool, the description covers the basic action. However, it lacks details on return values, error handling, and differentiation from sibling tools, which an agent would need for robust invocation.

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?

Although the schema already describes the 'task_name' parameter, the description adds value by indicating that the tool performs a search by name before deletion, which is not explicit in the schema. This helps the agent understand the lookup behavior.

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 ('delete'), the resource ('task from Todoist'), and the specific method ('by searching for it by name'). It distinguishes from sibling tools like todoist_complete_task and todoist_update_task by focusing on deletion.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., todoist_complete_task for marking done, todoist_update_task for editing). No prerequisites, edge cases, or contexts are mentioned.

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

todoist_get_tasksA

Get a list of tasks from Todoist with various filters

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum number of tasks to return (optional)
`filter`	No	Natural language filter like 'today', 'tomorrow', 'next week', 'priority 1', 'overdue' (optional)
`priority`	No	Filter by priority level (1-4) (optional)
`project_id`	No	Filter tasks by project ID (optional)

TDQS

A3.5/5.0

Behavior2/5

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

No annotations; description only mentions filters without disclosing read-only nature, pagination, or response structure.

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?

Single, concise sentence with no extraneous information.

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?

While schema covers parameters, missing output schema and no mention of pagination or error handling leaves gaps for a retrieval 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 provides 100% coverage with descriptions; the tool description adds negligible value over the schema.

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 tool retrieves a list of tasks with filters, distinct from CRUD siblings.

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?

Implied retrieval usage but no explicit when-to-use or when-not-to-use guidance compared to siblings.

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

todoist_update_taskB

Update an existing task in Todoist by searching for it by name and then updating it

ParametersJSON Schema

Name	Required	Description
`content`	No	New content/title for the task (optional)
`priority`	No	New priority level from 1 (normal) to 4 (urgent) (optional)
`task_name`	Yes	Name/content of the task to search for and update
`due_string`	No	New due date in natural language like 'tomorrow', 'next Monday' (optional)
`description`	No	New description for the task (optional)

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose behaviors. It mentions 'search by name' but fails to explain ambiguity handling (e.g., multiple matches), partial vs full update, side effects, or authorization needs. Lacks critical behavioral context.

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?

Single sentence that is front-loaded with the primary action. No unnecessary words, though slightly more structure could improve readability. Good conciseness overall.

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

Completeness2/5

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

No output schema, so description should cover return values. It does not mention what the tool returns (e.g., updated task object, success flag). Missing details on search behavior and partial update semantics make it incomplete for a mutation 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%, so baseline is 3. The description adds minimal value beyond the schema—only clarifying 'search by name' which is already implied by the task_name parameter description. No extra context for optional parameters.

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 verb 'Update', the resource 'existing task', and the method 'by searching for it by name'. It distinguishes from sibling tools like create, delete, complete, and get tasks.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives. There is no mention of using todoist_complete_task for completion or delete for removal, leaving the agent to infer from sibling tool names alone.

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

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0

Disambiguation5/5

Each tool targets a distinct operation (create, read, update, delete, complete) on tasks, with no overlap. The descriptions clearly differentiate the actions.

Naming Consistency5/5

All tools follow a consistent 'todoist_verb_task' pattern (e.g., todoist_complete_task, todoist_create_task), using snake_case and clear verbs.

Tool Count5/5

With 5 tools, the set covers the essential CRUD operations plus a completion action, which is appropriate for a task management server. No excessive or missing tools.

Completeness4/5

The tools cover full CRUD (create, get, update, delete) and a common operation (complete), which is sufficient for basic task management. Minor gaps like reordering or sharing tasks are not critical.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

mcp
net.todoist
Official Todoist MCP server for AI assistants to manage tasks, projects, and workflows.
App Automation Workplace & Productivity Project Management
2
acme-todo
com.ritzademo
An MCP server for a simple todo list
Developer Tools App Automation
2
Remote Desktop Commander
app.desktopcommander
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Shell Access OS Automation
214
Todo MCP A
io.github.AnkitPat
Create, list, and complete todo items through MCP.
Project Management Workplace & Productivity
1

Related MCP Servers

Todoist MCP Server
Project Management App Automation
greirson
A
license
B
quality
C
maintenance
An MCP server that connects Claude with Todoist for complete task and project management through natural language.
Updated 4 months ago (2026-05-01 10:23 UTC)
86
184
243
MIT
Enhanced Todoist MCP Server
App Automation Project Management
vitalio-sh
A
license
B
quality
D
maintenance
A comprehensive MCP server that provides full integration between Claude and Todoist, enabling task, project, section, and label management through 24 different tools with the complete Todoist API.
Updated 7 months ago (2026-02-15 19:57 UTC)
30
18
6
MIT
todoist-mcp-server
Project Management Workplace & Productivity
sjvadrevu
A
license
Not graded
quality
D
maintenance
A custom MCP server that connects Claude to Todoist using a permanent API token, avoiding OAuth re-authentication issues across all Claude surfaces.
Updated 5 months ago (2026-04-12 08:20 UTC)
52
MIT
Todoist MCP Server
Project Management Workplace & Productivity
stevesimpson418
A
license
A
quality
C
maintenance
A local MCP server for Todoist task management, enabling Claude to create, read, update, complete, delete, and move tasks, manage projects and labels, and add comments via the Todoist REST and Sync APIs.
Updated a month ago (2026-08-05 01:44 UTC)
15
1
MIT

Appeared in Searches

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/abhiz123/todoist-mcp-server'

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