Most lists like this were written once and never re-checked, so they still describe servers that stopped working. This one carries the date it was last checked, and says plainly where we could not confirm something.
| App | Status | What you should know |
|---|---|---|
| Todoist | First-party server | Official server. Setup steps for Claude and ChatGPT, plus the limits nobody documents. |
| Trello | Community servers | No first-party server. Which community option to pick, and the board-permission traps. |
| monday.com | Unconfirmed | Board and item access through MCP, plus the GraphQL complexity limits that stall long runs. |
| ClickUp | Unconfirmed | The hierarchy is what breaks ClickUp MCP setups. Here is how to scope it so it works. |
| Asana | Unconfirmed | Project and task access through MCP, plus the permission boundaries teams run into. |
| Obsidian | Community servers | Vault access for Claude: how the servers reach your notes, and the write risks to plan for. |
| Notion | First-party server | Official server. Why it sees nothing until you share pages, and where database writes get hard. |
| TickTick | Community servers | The OAuth step is where TickTick setups fail. What the API covers, and what it does not. |
| Google Tasks | Community servers | The smallest API in this list, which makes it the easiest MCP connection to get right. |
| Microsoft To Do | Community servers | Runs on Microsoft Graph, so your work tenant, not the server, decides what is possible. |
| Apple Reminders | Community servers | No cloud API, so access is local to your Mac through scripting. Private, but Mac-only. |
| Things 3 | Community servers | Writing to Things 3 is easy; reading from it is the hard part. Here is why. |
First-party means the company publishes its own server. Community means one or more servers exist on GitHub, maintained by volunteers. Unconfirmed means we could not verify a first-party server when we last checked — a statement about our checking, not a claim that none exists.
No jargon: what a connection is, which task apps work today, and how to stay safe.
What it takes, which apps support it today, and the simpler options when setup stalls.
The whole picture in one table: first-party, community, or nothing, and what each one allows.
Three signals separate a server that will still work next month from one that already does not: commits inside the last couple of months, a README that lists the exact tools the server exposes, and a stated authentication model that names the permissions it needs. Anything asking for a token without saying what it does with it is not worth installing.
Across every app here the pattern is the same. Reads are reliable nearly everywhere. Writes are where the differences live — exact status labels, typed custom fields, token scopes, recurring series. If you are choosing partly on this basis, test the one write you care about before you commit to anything.
No MCP server yet — we will not claim one before it exists. Webhooks, Zapier, Make and Apple Shortcuts work now, alongside tasks, habits, a focus timer and calendar sync. Developers can also use the LemTask task API directly.