To-Do List MCP Servers Compared: Todoist, TickTick, Mursa
What Claude can actually do with each server, how you sign in, and which permissions I would never hand an AI on day one
A to-do list MCP server lets Claude, Cursor, or another MCP client read and change your tasks. Todoist has an official hosted server that logs in with OAuth, so there is no key to manage. TickTick has no official server I could find, only community projects that need your own developer app. Mursa ships its own server that also covers calendar, notes, goals, and Gmail, with scoped keys that expire. Start read-only, keep approval on for anything that writes, and never auto-approve a delete.
Mursa's MCP server can create, update, complete, defer, and schedule a task. It cannot delete one. There is no delete-task tool in its list; the only delete it has is delete_goal, for goals. When I went through the official Todoist server and the two most popular TickTick servers to write this comparison, that was the first thing I looked for in each of them, because it tells you more about a server than its feature list does: what happens on the day the model misreads you.
Quick answer: a to-do list MCP server is a small connector that lets Claude or Cursor read and change your tasks. If you already use Todoist, use Doist's official hosted server, it logs in with OAuth and needs no API key. TickTick only has community servers. Mursa's server adds calendar, notes, goals, and Gmail to the same connection.
This is not a list of every MCP server on GitHub. It is a close read of three: what each one actually lets the model do, how you log in, how long setup takes, and what I would keep switched off on day one. I read each server's own documentation and source rather than a directory listing, and I name the exact repositories so you can check them yourself, because these projects change every few weeks.
What a To-Do List MCP Server Actually Does
MCP, the Model Context Protocol, is a standard way for an AI client to call tools that live outside the chat. A to-do list MCP server is one of those tool bundles. It exposes actions such as find tasks due today, create a task, or mark a task complete, and the model decides which ones to call based on what you ask. Your tasks stay in your app. The server is the doorway, and the tools are the things the model is allowed to do once it walks through.
That distinction matters more than it sounds. Two servers can both say they support tasks and still give the model very different powers. One might only let it read a single project at a time. Another might let it search every task you have, reschedule a batch of them, and delete a whole project in one call. The tool list is the real product, so that is what this comparison is built on.
It also explains why the same request works well with one server and badly with another. Ask for everything due today and a server with a date-based tool answers in one call. A server without one has to open every project and filter, which is slower, uses more of your context window, and gives the model more chances to miss something.
The Three Servers at a Glance
Todoist: official, hosted, OAuth
Doist publishes the server itself, MIT licensed, at github.com/todoist/todoist-mcp, and hosts it at ai.todoist.net/mcp. You sign in with your Todoist account through OAuth, so there is no key to copy or rotate. Its source folder has close to 50 tool modules covering tasks, projects, sections, labels, filters, comments, reminders, completed tasks, and productivity stats. The repository was updated the day before I checked it in November 2026.
TickTick: community servers only
I could not find an official TickTick server. The most starred community one is jacepark12/ticktick-mcp, a Python server with about 300 GitHub stars whose last code push I could see was in July 2025. A more recently updated option is alexarevalo9/ticktick-mcp-server, a TypeScript server last updated in September 2026. Both talk to TickTick's official Open API, and both need you to register your own app in TickTick's developer portal first.
Mursa: one server, seven resources
Mursa's server exposes 28 tools across tasks, calendar, goals, notes, habits, projects, and Gmail. You create a key in Mursa, choose its scopes and expiry, and run one npx command that configures Claude Code, Claude Desktop, and Cursor for you. Habits and projects are read-only for now, and Gmail tools only work after you connect Gmail in Mursa's settings.
Tool Coverage: What Claude Can Do With Each
Here is the capability comparison, written from each server's own tool list rather than its marketing copy. Where a TickTick answer depends on which community server you pick, I say so.
- See what is due today: Todoist has a find-tasks-by-date tool. On TickTick, jacepark12's server has get_tasks_due_today and get_overdue_tasks, while alexarevalo9's server only returns tasks project by project. Mursa has list_myday, list_schedule, and list_inbox.
- Create, update, and complete tasks: all three can.
- Reschedule: Todoist has a reschedule-tasks tool. Mursa has defer_task and schedule_task. The TickTick servers change dates through update_task.
- Search across tasks: Todoist has find-tasks and search. jacepark12's TickTick server has search_tasks. Mursa has search_tasks.
- Delete: Todoist has one delete-object tool that can remove a task, project, section, comment, label, filter, or reminder, and its source marks it as destructive. Both TickTick servers have delete_task and delete_project. Mursa has no delete-task tool. Its only delete is delete_goal.
- Calendar events: only Mursa, through list_calendar and create_calendar_event. Neither the Todoist tool list nor the TickTick tool lists include calendar events.
- Notes and goals: only Mursa has tools for both.
- Habits: Mursa can read them through list_habits. TickTick has habits in the app, but neither community server's tool list exposes them.
- Email: only Mursa, with list_emails, get_email, get_attachment, search_emails, send_email, and reply_email once Gmail is connected.
- Project health and productivity stats: only Todoist, with tools such as get-productivity-stats and get-project-health.
If your tasks already live in Todoist, its official server beats everything else here on three counts: you log in with OAuth instead of managing a key, it is maintained by the company that owns the API, and it has the deepest task and project tooling, including stats and project health. Switching task apps to get a better MCP server would be backwards.
The pattern in that list is the real decision. Todoist goes deep on tasks and projects. The TickTick servers cover the basics of tasks and projects and little else. Mursa goes wide: fewer project-management tools than Todoist, but tasks, calendar, notes, goals, and email behind one connection, which matters for workflows that cross those lines.
Login and Setup: OAuth, API Key, or Your Own Developer App
Setup is where the three differ most, and it decides whether a non-developer can use them at all.
Todoist is the easiest. In Claude Code, the official plugin wires everything up: run /plugin marketplace add todoist/todoist-mcp, then /plugin install todoist@doist, and OAuth opens in your browser the first time a Todoist tool runs. If you prefer the manual route, run claude mcp add --transport http todoist https://ai.todoist.net/mcp, then open /mcp inside Claude and authenticate. In Claude Desktop, go to Settings, Connectors, Add custom connector, and paste the same URL. You can revoke access later in Todoist under Settings, Integrations.
TickTick asks the most of you. Both community servers start the same way: create an account on TickTick's developer portal, register an application, and set its OAuth redirect URL to http://localhost:8000/callback. With jacepark12's server you then run its auth command through uv, a browser window asks you to approve access, and the tokens are saved to a local .env file and refreshed automatically. With alexarevalo9's server you approve access in the browser, then copy the access token it shows into an environment variable yourself. Neither is hard for a developer. Both are a wall for anyone who has never seen a terminal.
Mursa sits in between. You open Settings, API keys in Mursa, click New key, choose what the key may do and when it expires, and copy it once, since it starts with mursa_mcp_ and is never shown again. Then you run npx -y mursa-mcp setup --key=YOUR_KEY in a terminal. That one command sets Mursa up in Claude Code, Claude Desktop, and Cursor, and the only requirement is Node 18 or newer. Restart your client and ask it to run whoami, which should return your Mursa account. There is a manual JSON config for other clients, but there is no OAuth sign-in, so you are managing a key.
Whichever server you install, make the first call a harmless read: who am I, what is due today, list my projects. If that returns the right account and the right data, you know the connection points at the account you think it does, before anything gets created or changed.
Three Workflows Worth Setting Up, With Copy-Paste Prompts
Connecting a server is the easy part. The value comes from two or three routines you actually repeat. These are the three I would start with. Each prompt asks the model to propose before it writes, which matters more than any setting.
1. Morning triage. Paste this at the start of the day: "Look at everything due today and everything overdue. Group it into must do today, can move, and should not be on my list at all. For anything in can move, suggest a new date. Do not change anything yet. Show me the plan and wait for my yes." Todoist handles this in one or two calls. jacepark12's TickTick server can do it with its due-today and overdue tools. alexarevalo9's has to read each project first. Mursa uses list_myday and list_schedule, and because it can also read your calendar, it can tell you that the slot you planned for a task is already taken by a meeting.
2. Turning an email into a task. This one is where email access changes everything: "Search my email from the last two days for anything where someone asked me to do something by a date. For each one, draft a task with a clear title, the due date, and the sender's name in the description. List them for my approval before creating any." Mursa can do the whole thing inside one server, with search_emails followed by create_task. With Todoist or TickTick you need a separate email connector alongside the task server, which works, but now two tools hold your data and the model has to stitch them together. I wrote more about why the extraction step is harder than it looks in how AI reads your inbox and creates tasks.
3. End-of-day review. Run it before you close the laptop: "List what I completed today and what I did not. For anything unfinished, ask me one question: move it, break it down, or drop it. Then apply only the changes I confirm, and summarise tomorrow's first three tasks." On Todoist the completed-tasks and stats tools make the first half rich. On Mursa the same prompt can also pull tomorrow's calendar, so the first three tasks come out sized to the time you actually have.
Notice what all three prompts have in common. They separate thinking from writing. The model reads, proposes, and waits, and only then calls a write tool. That one habit removes most of the risk in the next section.
Safety: What I Keep Read-Only and Why
Giving a model write access to your tasks is low stakes until it is not. A wrong due date is annoying. A deleted project, or an email sent on your behalf to the wrong person, is not. These are the rules I follow, and they apply to every server here.
- Start read-only for a week. On Mursa, create the first key with read scopes only, such as tasks:read and calendar:read. Todoist's OAuth flow does not show per-tool scopes in its setup docs, so lean on your client's approval prompts instead.
- Never auto-approve a destructive tool. Todoist's delete-object can remove a whole project, the TickTick servers have delete_project, and Mursa has delete_goal. Most clients can ask before each tool call, so keep that on for anything that deletes or sends.
- Treat email sending as its own decision. Mursa splits reading Gmail (email:read) from sending (email:send) and limits sends to 5 a minute. Leave the send scope off unless a workflow genuinely needs it.
- Watch for instructions hiding in content. A task description or an email can contain text that reads like a command. A server that can both read email and send email should never act on instructions it found inside a message. Your prompt should say so explicitly.
- Give keys a shelf life. Mursa keys can expire, are stored hashed, and stop working on the next call after you revoke them. TickTick tokens live in a local .env file, so treat that file like a password. For Todoist, revoke the connection under Settings, Integrations when you stop using it.
Rate limits are a quieter safety net. Mursa caps reads at 60 a minute and writes at 30 a minute, which stops a confused model from rewriting your entire list in a loop. It also keeps an audit log of every call, with the action, status, and timing, for 90 days, without storing the payload. If you ever wonder what the model actually did, that log answers it.
The tool list is the real product. Read it before you connect anything, and look for the delete tool first.
Which One Should You Pick?
The honest answer is that the server should follow the task app, not the other way around. Moving your whole task system to get a nicer MCP connection is a bad trade. Here is how I would decide.
- You already use Todoist: install the official server and stop reading comparisons. OAuth, maintained by Doist, the deepest task tooling here.
- You use TickTick and you are comfortable in a terminal: start with jacepark12's server for its date and priority tools, knowing it has not seen a code push since mid 2025. If you want something updated more recently, alexarevalo9's server is the alternative, with a smaller tool set.
- You use TickTick and you are not technical: wait. Registering a developer app and handling tokens is a real barrier, and there is no hosted option I could find.
- Your work crosses tasks, calendar, and email: this is the case Mursa's server was built for, since one connection covers all three and the email-to-task workflow does not need a second connector.
If you are still choosing the task app itself, the MCP server is a tiebreaker, not the main event. My longer Todoist vs TickTick vs Mursa comparison covers the parts that matter more day to day: capture speed, planning, and what each costs you in attention.
Where Mursa Fits, Honestly
Mursa's server is built around one idea: the workflows that matter cross app boundaries. The email that creates a task, the task that needs a calendar slot, the goal that a week of tasks is supposed to move. With separate connectors for each, the model spends half its effort stitching. With one server that holds tasks, calendar, notes, goals, and Gmail, the morning triage and email-to-task prompts above become a single conversation.
It has real gaps. You manage a key instead of signing in with OAuth, which Todoist does better. Habits and projects are read-only for now. It does not have Todoist's project health or productivity stats tools. And if you are deep in Todoist already, its own server is the better choice for you, full stop. The full tool list and setup steps are on the Mursa MCP page.
If you have been weighing which AI assistant to pair with any of these, I compared the two main subscriptions on real work in ChatGPT Plus vs Claude Pro. Whichever you pick, the setup advice is the same: read the tool list, start read-only, and let the model propose before it writes.
Frequently Asked Questions
What is a to-do list MCP server?
It is a connector that uses the Model Context Protocol to let an AI client such as Claude, Claude Code, or Cursor call tools on your task app, for example find tasks due today, create a task, or mark one complete. Your tasks stay in the app; the server only exposes actions the model can take.
Does Todoist have an official MCP server?
Yes. Doist publishes it as an open-source, MIT-licensed project and hosts it at ai.todoist.net/mcp. You sign in with your Todoist account through OAuth, so there is no API key to manage, and you can revoke access under Settings, Integrations in Todoist.
Is there an official TickTick MCP server?
I could not find one as of November 2026. The options are community projects such as jacepark12/ticktick-mcp and alexarevalo9/ticktick-mcp-server. Both use TickTick's official Open API and require you to register your own app in TickTick's developer portal before you can sign in.
How do I connect Claude to Mursa?
Create an API key in Mursa under Settings, API keys, choosing its scopes and expiry, then run npx -y mursa-mcp setup --key=YOUR_KEY. It configures Claude Code, Claude Desktop, and Cursor automatically and needs Node 18 or newer. Restart your client and run whoami to confirm.
Can an MCP server delete my tasks?
It depends on the server. Todoist's official server has a delete tool that can remove tasks and whole projects, and the TickTick community servers have delete_task and delete_project. Mursa's server has no delete-task tool, though it can delete goals through delete_goal. Keep approval prompts on for any destructive tool.
Which to-do MCP server works best for email to task workflows?
One that can read email and create tasks in the same connection. Mursa's server includes Gmail tools alongside task tools once Gmail is connected, so search_emails and create_task run in one conversation. With Todoist or TickTick you need a separate email connector next to the task server.