MCP server for Todoist task and project management, with tools for tasks, subtasks, projects, sections, labels, comments, reminders, filters, activity, backups, collaboration, bulk operations, and dry-run testing.
Todoist MCP Server can create, update, delete, complete, reopen, reorder, archive, and bulk-modify tasks, subtasks, projects, sections, labels, comments, reminders, filters, shared labels, and collaboration state., Bulk create, bulk update, bulk delete, bulk complete, project deletion, section deletion, label deletion, reminder changes, and duplicate merge operations can alter many Todoist records at once., Dry-run mode simulates mutation operations but still queries real Todoist data for validation., Pro and Business features such as reminders, filters, shared labels, collaboration, backups, and workspace operations may expose or modify team data., Require confirmation before deleting tasks or projects, changing due dates in bulk, completing groups of tasks, modifying shared projects, creating reminders, downloading backups, or changing collaboration state.
Privacy notes
Todoist API tokens, task IDs, project IDs, section IDs, label IDs, reminder IDs, comment IDs, user IDs, collaborator details, activity logs, completed tasks, backups, and productivity statistics can be exposed to the MCP client., Task names, descriptions, comments, due dates, deadlines, labels, reminders, attachments, project notes, and completed-task history can contain private work or personal planning data., Bulk and filter tools may reveal larger slices of a Todoist workspace than a single-task request., Backup download tools can expose a broad historical snapshot of Todoist data., Keep Todoist tokens in local MCP configuration only, and avoid sharing MCP logs, dry-run traces, or transcripts that include private task or project data.
Author
greirson
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 5 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.
4 areas
SafetyGeneralTodoist MCP Server can create, update, delete, complete, reopen, reorder, archive, and bulk-modify tasks, subtasks, projects, sections, labels, comments, reminders, filters, shared labels, and collaboration state.
SafetyGeneralBulk create, bulk update, bulk delete, bulk complete, project deletion, section deletion, label deletion, reminder changes, and duplicate merge operations can alter many Todoist records at once.
SafetyExecution & processesDry-run mode simulates mutation operations but still queries real Todoist data for validation.
SafetyGeneralPro and Business features such as reminders, filters, shared labels, collaboration, backups, and workspace operations may expose or modify team data.
SafetyNetwork accessRequire confirmation before deleting tasks or projects, changing due dates in bulk, completing groups of tasks, modifying shared projects, creating reminders, downloading backups, or changing collaboration state.
PrivacyCredentials & tokensTodoist API tokens, task IDs, project IDs, section IDs, label IDs, reminder IDs, comment IDs, user IDs, collaborator details, activity logs, completed tasks, backups, and productivity statistics can be exposed to the MCP client.
PrivacyExecution & processesTask names, descriptions, comments, due dates, deadlines, labels, reminders, attachments, project notes, and completed-task history can contain private work or personal planning data.
PrivacyNetwork accessBulk and filter tools may reveal larger slices of a Todoist workspace than a single-task request.
PrivacyNetwork accessBackup download tools can expose a broad historical snapshot of Todoist data.
PrivacyCredentials & tokensKeep Todoist tokens in local MCP configuration only, and avoid sharing MCP logs, dry-run traces, or transcripts that include private task or project data.
Disclosure: Community-maintained MIT MCP server for the Todoist API. Todoist is a separate task-management service; users must follow Todoist API, account, workspace, and plan restrictions.
Safety notes
Todoist MCP Server can create, update, delete, complete, reopen, reorder, archive, and bulk-modify tasks, subtasks, projects, sections, labels, comments, reminders, filters, shared labels, and collaboration state.
Bulk create, bulk update, bulk delete, bulk complete, project deletion, section deletion, label deletion, reminder changes, and duplicate merge operations can alter many Todoist records at once.
Dry-run mode simulates mutation operations but still queries real Todoist data for validation.
Pro and Business features such as reminders, filters, shared labels, collaboration, backups, and workspace operations may expose or modify team data.
Require confirmation before deleting tasks or projects, changing due dates in bulk, completing groups of tasks, modifying shared projects, creating reminders, downloading backups, or changing collaboration state.
Privacy notes
Todoist API tokens, task IDs, project IDs, section IDs, label IDs, reminder IDs, comment IDs, user IDs, collaborator details, activity logs, completed tasks, backups, and productivity statistics can be exposed to the MCP client.
Task names, descriptions, comments, due dates, deadlines, labels, reminders, attachments, project notes, and completed-task history can contain private work or personal planning data.
Bulk and filter tools may reveal larger slices of a Todoist workspace than a single-task request.
Backup download tools can expose a broad historical snapshot of Todoist data.
Keep Todoist tokens in local MCP configuration only, and avoid sharing MCP logs, dry-run traces, or transcripts that include private task or project data.
Prerequisites
Todoist API token from Todoist integrations developer settings.
Node.js 18 or newer for the npm stdio server.
Review of whether the token has access to personal, shared, Pro, Business, or workspace features.
Optional `DRYRUN=true` for simulating mutation tools while still validating against real Todoist data.
Optional `TODOIST_UNIFIED_TOOLS=true` when the consolidated 19-tool interface is preferred over the legacy 60-plus-tool surface.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
beginner
Tool listing metadata
Disclosure
Community-maintained MIT MCP server for the Todoist API. Todoist is a separate task-management service; users must follow Todoist API, account, workspace, and plan restrictions.
Todoist MCP Server connects Claude and other MCP clients to Todoist through the
Todoist API. It supports task, project, section, label, comment, reminder,
filter, activity, backup, collaboration, completed-task, shared-label, and bulk
operation workflows.
Use it when Claude needs supervised access to personal or team Todoist planning
workflows, especially when dry-run testing is useful before applying changes.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, npm metadata, license, package metadata, tool reference, server
entrypoint, dry-run wrapper, unified tool registry, and MCPB manifest for
current setup and behavior details.
Features
Manage Todoist tasks with create, get, update, delete, complete, reopen, and
quick-add actions.
Run bulk create, update, delete, and complete operations across multiple
matching tasks.
Remove DRYRUN or set it to false only after testing the target workflow.
Use Cases
Review today's tasks, overdue tasks, or high-priority work.
Create tasks from meeting notes with due dates, labels, priorities, and
sections.
Simulate bulk cleanup or due-date changes before applying them.
Add comments or project notes during review and planning.
Summarize Todoist activity, completed work, productivity stats, or backups.
Manage shared projects, collaborators, workspace labels, filters, and
reminders with explicit confirmation.
Safety and Privacy
Todoist MCP Server can modify real task and project data. Start with
DRYRUN=true, require confirmation before destructive or bulk operations, and
be especially careful with shared projects, reminders, backups, workspace
labels, and collaboration tools.
Treat Todoist API tokens, IDs, task names, descriptions, comments, due dates,
deadlines, labels, reminders, completed-task history, backups, collaborators,
activity logs, and productivity statistics as sensitive personal or team data.
Keep credentials and transcripts out of shared configs and public examples.
Show that Todoist MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/todoist-mcp-server)
How it compares
Todoist MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
MCP server for Todoist task and project management, with tools for tasks, subtasks, projects, sections, labels, comments, reminders, filters, activity, backups, collaboration, bulk operations, and dry-run testing.
MCP server for Trello boards, cards, lists, comments, checklists, attachments, labels, board activity, workspace selection, and rate-limited Trello API automation from Claude.
MCP server for Anki flashcards that lets Claude review cards, manage decks, create and update notes, handle tags and media, inspect stats, and drive Anki desktop GUI workflows.
Official LINE MCP server that connects Claude and other AI agents to the LINE Messaging API for push messages, broadcasts, profile lookup, quotas, follower IDs, and rich-menu management.
✓Todoist MCP Server can create, update, delete, complete, reopen, reorder, archive, and bulk-modify tasks, subtasks, projects, sections, labels, comments, reminders, filters, shared labels, and collaboration state.
Bulk create, bulk update, bulk delete, bulk complete, project deletion, section deletion, label deletion, reminder changes, and duplicate merge operations can alter many Todoist records at once.
Dry-run mode simulates mutation operations but still queries real Todoist data for validation.
Pro and Business features such as reminders, filters, shared labels, collaboration, backups, and workspace operations may expose or modify team data.
Require confirmation before deleting tasks or projects, changing due dates in bulk, completing groups of tasks, modifying shared projects, creating reminders, downloading backups, or changing collaboration state.
✓Trello MCP Server can create, read, update, move, archive, and delete board data depending on token permissions and requested tools.
Card, checklist, label, due-date, start-date, comment, attachment, board, list, workspace, and active-board changes can affect real team workflows.
File attachments are added from URLs; review source URLs and destination cards before allowing an agent to attach files.
Use `TRELLO_ALLOWED_WORKSPACES` to limit workspace access, especially when a token can see personal, client, or production boards.
Require confirmation before creating boards, adding attachments, deleting or archiving cards, changing due dates, moving cards between lists, or posting comments on behalf of a user.
✓Anki MCP Server can create, update, delete, move, tag, rate, and sync cards and notes through AnkiConnect.
Destructive tools include note deletion, media deletion, unused-tag clearing, deck moves, tag replacement, model styling changes, and review rating actions that affect scheduling.
The server supports read-only mode that blocks exposed write actions, but users should still review tool calls before enabling unrestricted study or collection-management workflows.
Media tools can store files from local paths, URLs, or base64 data and can retrieve media as base64 content.
GUI tools can open Anki windows, select cards, edit notes, show answers, and undo the last Anki action.
Remote tunnel or ngrok-style setups expose local Anki to cloud-hosted AI clients and require careful authentication, origin, and URL-sharing controls.
✓LINE Bot MCP Server can push text and flex messages to users, broadcast messages to all followers, retrieve follower IDs, inspect profiles, check message quotas, create rich menus, set default rich menus, cancel defaults, and delete rich menus.
Broadcast and rich-menu tools can affect every user following the connected LINE Official Account, so require human approval before running them in production.
Push-message tools can contact individual users directly; confirm the target `userId`, message body, and account context before sending.
Rich-menu tools can upload generated menu images and change user-facing navigation for the account.
Use least-privilege channel tokens where possible, keep test and production LINE accounts separate, and monitor quota consumption.
The upstream README marks the project as a preview version for experimental use with potentially incomplete functionality or support.
Privacy notes
✓Todoist API tokens, task IDs, project IDs, section IDs, label IDs, reminder IDs, comment IDs, user IDs, collaborator details, activity logs, completed tasks, backups, and productivity statistics can be exposed to the MCP client.
Task names, descriptions, comments, due dates, deadlines, labels, reminders, attachments, project notes, and completed-task history can contain private work or personal planning data.
Bulk and filter tools may reveal larger slices of a Todoist workspace than a single-task request.
Backup download tools can expose a broad historical snapshot of Todoist data.
Keep Todoist tokens in local MCP configuration only, and avoid sharing MCP logs, dry-run traces, or transcripts that include private task or project data.
✓Trello API keys, tokens, board IDs, workspace IDs, card IDs, member names, labels, comments, checklists, attachments, due dates, and activity logs can be exposed to the MCP client.
Active board and workspace selections may persist locally in Trello MCP configuration.
Card descriptions, comments, attachments, and activity histories can contain private customer, roadmap, incident, or operational data.
Proxy settings, Trello credentials, and workspace allowlists should be kept out of shared MCP configs, logs, screenshots, and transcripts.
Response previews reduce some large card-description exposure, but full-card and activity tools can still return sensitive Trello content.
✓Tool calls can expose deck names, note fields, card contents, tags, review history, media filenames, base64 media, selected notes, collection stats, scheduling metadata, and AnkiConnect errors.
Flashcards may contain medical, language-learning, school, work, personal, customer, or confidential study material.
Sync can send Anki collection changes to AnkiWeb according to the user's Anki account and sync settings.
Local media file paths, URLs imported into cards, and GUI-selected note IDs can enter MCP client context and model logs.
Remote tunnel providers and hosted clients may process connection metadata or traffic according to their own policies.
✓Channel access tokens, destination user IDs, follower IDs, profile display names, profile picture URLs, status messages, language, message contents, flex-message JSON, and rich-menu IDs can be exposed to the MCP client.
Broadcast prompts, generated messages, user IDs, and profile results may be retained in MCP client logs, terminal history, model context, or chat transcripts.
Treat LINE Official Account credentials and recipient identifiers as secrets, and avoid pasting real tokens or user IDs into shared logs.
Review LINE platform policies and internal consent requirements before retrieving follower IDs or using AI-generated outbound messages.
Prerequisites
Todoist API token from Todoist integrations developer settings.
Node.js 18 or newer for the npm stdio server.
Review of whether the token has access to personal, shared, Pro, Business, or workspace features.
Optional `DRYRUN=true` for simulating mutation tools while still validating against real Todoist data.
Trello API key and token with access to the boards and workspaces Claude may use.
Bun-compatible published package runtime or an MCP client that can launch the packaged stdio server through npx.
Optional `TRELLO_BOARD_ID` or `TRELLO_WORKSPACE_ID` when a default board or workspace should be selected at startup.
Optional `TRELLO_ALLOWED_WORKSPACES` to constrain the token to specific approved Trello workspaces.
Anki Desktop installed and running.
The AnkiConnect add-on installed in Anki.
Node.js 22.12 or newer for the npm package path.
Review of which decks, cards, tags, media files, and note types the MCP client may access.
Node.js 22 or newer for the published npm package.
A LINE Official Account with the Messaging API enabled.
A LINE channel access token with the permissions needed for the intended tools.
A destination user ID when using the default recipient flow for push-message tools.