Provides tools for interacting with a user's Todoist account, enabling AI agents to list projects, sections, and labels, and to browse, filter, and retrieve tasks/to-do items with their details such as content, description, priority, due dates, labels, and web URLs.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Todoist MCP Pack list my Todoist tasks due today and anything overdue"
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.
Todoist MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
Tool | Description |
| List all projects in the user's Todoist account. Returns each project's id, name, color, favorite status, web URL, and parent project id. Use to discover projects and their ids before listing tasks or sections. |
| List active (incomplete) tasks / to-do items from Todoist. Optionally filter by a project id, or by a Todoist filter query (a powerful query language, e.g. "today | overdue", "p1 & #Work", "no date"). Returns each task's id, content, description, project id, priority, due date/datetime, labels, and web URL. |
| Get the full details of a single Todoist task / to-do item by its id, including content, description, project id, section id, priority, due date/datetime, labels, web URL, and creation time. Use after todoist_list_tasks to inspect one task. |
| List the sections within a Todoist project. Sections group tasks inside a project. Returns each section's id, project id, name, and order. Use to understand how tasks in a project are organized. |
| List all personal labels in the user's Todoist account. Labels are tags applied to tasks. Returns each label's id, name, color, and favorite status. Use to discover labels for filtering or interpreting task labels. |
Related MCP server: Todoist MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"todoist": {
"url": "https://gateway.pipeworx.io/todoist/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/todoist/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1684+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This pack runs against a connected todoist account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect todoist, then call POST https://gateway.pipeworx.io/v1/tools/todoist_list_projects with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/todoist_list_projects. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"todoist": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-todoist"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-todoistIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Todoist data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Official Todoist MCP server for AI assistants to manage tasks, projects, and workflows.
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Manage Superlist tasks and lists in plain language from any MCP-compatible AI agent.
