Menu
Mattering Automations connector

A Todoist MCP built on the API Todoist actually runs now

Connect one API token and Todoist becomes workflow steps: projects, tasks with Todoist's filter query language and natural language quick add, sections, labels, and comments. Built on the current unified v1 API, not the deprecated REST v2, so the ids and pagination match what Todoist speaks today.

35 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Todoist MCP connector does

The Todoist connector for Mattering Automations is 35 nodes on the unified API v1: projects (list, get, create, update, archive, unarchive, delete, plus collaborators), tasks (list, list by Todoist's filter query language, list completed, get, create, quick add in natural language, update, move, close, reopen, delete), sections (full CRUD), labels including shared labels (six nodes), and comments (full CRUD).

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer what is due today, add a task the way you would type it, and close what got done, without anyone opening Todoist.

The API surface matters here: Todoist replaced its REST v2 and Sync v9 APIs with a unified v1 at api.todoist.com/api/v1, with new opaque string ids that the old numeric ids do not survive into. This connector is built entirely on the current surface, with its cursor pagination modeled everywhere, so it works with the ids Todoist hands out today instead of the ones it is retiring.

The marquee node is Todoist: Quick Add Task (Natural Language): it accepts exactly what a person would type into Todoist, like a phrase containing tomorrow at 4pm with a project shortcut and a priority, and Todoist parses the due date, project, labels, and priority out of it. For an AI assistant, that means adding a task is one natural sentence, not six structured fields. Nothing in the connector is riskier than a delete, all five deletes are flagged, and close and archive both have documented inverses, so they are modeled as reversible.

One connection, three surfaces

  • Visual automations. Drag Todoist nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Todoist node, ready to drop on the canvas

35 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 14

Todoist: Get Comment

Return one comment by ID, including its content, author, post time, and attachment metadata.

Todoist: Get Label

Return one personal label by ID, including its name, color, order, and favorite flag.

Todoist: Get Project

Return one project by its opaque string ID, including name, color, view style, sharing state, and hierarchy position.

Todoist: Get Section

Return one section by its opaque string ID, including its name, project, order, and archived state.

Todoist: Get Task

Return one active (non-completed) task by ID, including content, due and deadline objects, labels, priority, and its project/section/parent placement.

Todoist: List Comments

Get all comments of one task OR one project, paginated. Provide exactly one of task_id or project_id; providing neither or both is an error. File attachments arrive as metadata objects with a file_url, never inline file content.

Todoist: List Completed Tasks

Get tasks completed within a date-time range of up to 3 months, paginated - the building block for done-this-week digests and completion reports. Optionally narrowed by workspace, project, section, parent task, or a filter query. Note the page items arrive under an 'items' key on this endpoint.

Todoist: List Labels

Get all of the user's personal labels, paginated. Label NAMES (not ids) are what task label fields and the label filter expect.

Todoist: List Project Collaborators

Get all collaborators of a shared project, paginated. Collaborator user ids are what the task assignee_id field expects.

Todoist: List Projects

Get all active projects for the user, paginated. Works with an empty config (every account has at least the Inbox project), which is why it doubles as the credential health check. Project ids from here feed every project-scoped node.

Todoist: List Sections

Get active sections, paginated - all of them, or only those of one project via project_id.

Todoist: List Shared Labels

Get the unique shared label names currently in use on active tasks, paginated. Shared labels are names applied by collaborators that are not in the user's personal label list.

Todoist: List Tasks

Get active (uncompleted) tasks, paginated. All parameters are optional and combine to narrow the list: by project, section, parent task, label name, or an explicit id list. With no parameters it returns every active task the user can see.

Todoist: List Tasks by Filter Query

Get active tasks matching a Todoist filter query, paginated. Filters are Todoist's own query language: 'today | overdue', '#Work & p1', 'due before: next week', '@waiting'. One filter expression per call (the comma operator that combines several filters into tabs is not supported here).

Action nodes 21

Todoist: Archive Project

Archive a project and return it. Personal projects are archived only for the initiating user; workspace projects are archived for every workspace user. Reversible with Todoist: Unarchive Project, so this is not flagged destructive.

Todoist: Close Task

Complete a task, exactly like checking it off in the app: regular tasks (with their sub-tasks) move to history, and recurring tasks are rescheduled to their next occurrence. Reversible with Todoist: Reopen Task, so this is not flagged destructive. Returns null on success.

Todoist: Create Comment

Add a comment to one task OR one project and return it. Provide exactly one of task_id or project_id. An attachment is passed as a metadata object referencing an already-hosted file URL (this connector does not upload file bytes).

Todoist: Create Label

Create a personal label and return it. Free-plan label limits apply; exceeding them returns a premium-only error.

Todoist: Create Project

Create a new project and return it. Give a parent_id to nest it as a sub-project, or a workspace_id to create a workspace project instead of a personal one.

Todoist: Create Section

Create a new section inside a project and return it.

Todoist: Create Task

Create a new task with explicit typed fields and return it. Only content is required; without a project_id the task lands in the Inbox. For natural-language input ('Buy milk tomorrow #Shopping p1') use Todoist: Quick Add Task instead.

Todoist: Delete Comment

PERMANENTLY delete a comment. This cannot be undone. Returns null on success.

Todoist: Delete Label

PERMANENTLY delete a personal label and remove it from every task that carries it. This cannot be undone. Returns null on success.

Todoist: Delete Project

PERMANENTLY delete a project together with ALL of its sections and tasks. This cannot be undone; archive the project instead if you may need it back. Returns null on success.

Todoist: Delete Section

PERMANENTLY delete a section and ALL of its tasks. This cannot be undone. Returns null on success.

Todoist: Delete Task

PERMANENTLY delete a task and all of its sub-tasks. This cannot be undone; use Todoist: Close Task if completing it is enough. Returns null on success.

Todoist: Move Task

Move a task to another project, section, or under a parent task, and return the moved task. Provide exactly ONE of project_id, section_id, or parent_id as the destination.

Todoist: Quick Add Task (Natural Language)

Create a task from one natural-language string using the same Quick Add parser as Todoist's own apps: dates ('tomorrow at 5pm'), #Project, /Section, @label, priority p1-p4, +Assignee, {deadline}, !reminder, and '// description' in a single line. If part of the text fails to parse the task is still created with the unparsed text left in the content.

Todoist: Reopen Task

Uncomplete a task, restoring it (and any completed ancestor tasks or sections) from history to the end of the list inside its parent. Returns null on success.

Todoist: Unarchive Project

Restore an archived project to active, and return it. For workspace projects this makes it visible again to all applicable workspace users.

Todoist: Update Comment

Replace a comment's text content and return the updated comment.

Todoist: Update Label

Update a personal label's name, order, color, or favorite flag, and return it. Omitted fields are left unchanged; at least one field must be provided.

Todoist: Update Project

Update a project's name, description, color, favorite flag, view style, or position, and return the updated project. Omitted fields are left unchanged.

Todoist: Update Section

Update a section's name, order, collapsed state, or description, and return it. Omitted fields are left unchanged.

Todoist: Update Task

Update an existing task's fields and return it. Omitted fields are left unchanged. To change which project, section, or parent a task belongs to, use Todoist: Move Task - those fields are not updatable here.

Connecting Todoist takes one credential

Todoist issues personal API tokens from Settings, then Integrations, then the Developer tab. The token authenticates as you across all projects the account can see, and Mattering sends it as a bearer credential on every request.

1

In Todoist, open Settings, then Integrations, then Developer, and copy your API token.

2

In Mattering Automations, open Connectors, click Add Connector, choose Todoist, and create a credential with that token.

3

Click Test Connection. Mattering lists your projects, a safe read that always returns at least the Inbox, so it cleanly confirms the token works.

4

All 35 Todoist nodes appear in the canvas palette.

Common uses for the Todoist MCP

Tasks added the way people talk

Todoist: Quick Add Task (Natural Language) takes one line, exactly as you would type it in Todoist, and Todoist parses out the due date, project, labels, and priority. It is the natural endpoint for AI assistants and for workflows that turn messages or form submissions into tasks without mapping fields.

Filter queries as workflow inputs

Todoist: List Tasks by Filter Query runs Todoist's own filter language: today, overdue, seven-day windows, label and priority combinations. A morning workflow can pull the day's real agenda, or sweep overdue items into an escalation list, using the same queries power users already write.

Two-way sync with Mattering work

A scheduled sweep can mirror Todoist tasks into Mattering Productivity where the team plans, and completions flow back: closing the Mattering task drives Todoist: Close Task on the original. Because Todoist: Reopen Task exists, the loop is safe to run without fear of one-way mistakes.

Completed-task reporting

Todoist: List Completed Tasks returns what got done in a completion-date window. On a weekly schedule it becomes an automatic done list, landing in a Mattering database or a report task, with no one compiling it by hand.

Project scaffolding on demand

Todoist: Create Project, Todoist: Create Section, and a loop of task creates can stand up a templated project structure per client or per engagement, driven from records in a Mattering database. Archive rather than delete when it ends: Todoist: Archive Project has a documented inverse, and the five delete nodes are the only destructive things in the connector.

Comments as the audit trail

Todoist: Create Comment lets workflows say what they did on the task itself: why it was created, what changed, which automation touched it. Comment attachments arrive as file URL metadata, so payloads stay light.

Example: A morning agenda that files itself

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a schedule runs each weekday morning.

2

Todoist: List Tasks by Filter Query pulls tasks matching a today or overdue filter.

3

An AI step drafts a short agenda note grouping the tasks by project and priority.

4

The agenda lands as a comment on a standing task in Mattering Productivity, and urgent overdue items each get their own escalation task.

5

At day's end, a second pass runs Todoist: List Completed Tasks and appends what actually got done.

Todoist MCP questions, answered

What Todoist operations are supported?

35 nodes: projects (list, get, create, update, archive, unarchive, delete, list collaborators), tasks (list, list by filter query, list completed, get, create, quick add natural language, update, move, close, reopen, delete), sections (list, get, create, update, delete), labels (list, get, create, update, delete, plus shared labels), and comments (list, get, create, update, delete). Deliberately not shipped: the user endpoint (its response echoes the account's API token, which would copy the credential into execution records), the Sync protocol, reminders, and webhooks (Todoist configures those per OAuth app, not per token).

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. Quick add in particular is a natural fit: an assistant adds a task by writing the same sentence a person would type.

Which Todoist API is this built on, and why does it matter?

The unified API v1 at api.todoist.com/api/v1, which is Todoist's current surface; the older REST v2 and Sync v9 are deprecated and marked for removal. It matters because the migration changed id shapes: v1 uses opaque string ids, and old numeric ids from v2-era integrations are rejected. If you are moving automations from an older Todoist integration, expect to re-fetch ids through these nodes rather than reusing stored numeric ones.

How does natural language quick add work?

Todoist: Quick Add Task (Natural Language) sends your text to the same parser the Todoist apps use, so one line like a task description with tomorrow 4pm, a project shortcut, a label, and a priority marker becomes a fully structured task: due date, project, labels, and priority all parsed out. For anything a person or an assistant phrases naturally, it beats the structured Todoist: Create Task; use create when a workflow already has clean field values.

What can the filter query node express?

Todoist's full filter language: date windows like today or overdue, label and priority tests, project scoping, and boolean combinations of them. Todoist: List Tasks by Filter Query is the workflow twin of the saved filters power users build in the app, and the practical engine behind agenda, escalation, and review sweeps.

Is closing a task reversible? What about deletes?

Close is reversible: Todoist: Reopen Task is the documented inverse, so completion loops are safe to automate. Archive has Todoist: Unarchive Project as its inverse. The five delete nodes (task, project, section, label, comment) are the only destructive operations in the connector, and each is flagged; prefer close and archive in automated flows and keep deletes behind conditions.

How does pagination work on the list nodes?

Cursor-based, as the unified API defines it: list responses return results plus a next_cursor, and passing the cursor back with a limit of up to 200 fetches the next page. The completed-tasks endpoint is the one documented deviation (its results arrive under an items key), and the node's sample output shows that honestly. Note the completed list is windowed by completion date, up to about three months per query.

One thing to double-check: task priorities

Todoist's own v1 docs disagree with themselves on priority direction: the create documentation says 1 is highest, while the task object documentation says the API returns 4 for a p1 task. The connector follows the long-standing wire behavior (4 in the API means p1, urgent) and says so in the node help text. If a priority-driven workflow matters, verify against one real task before trusting the direction.

35 nodes waiting on the canvas

Put Todoist to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Todoist is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products