Every list of this kind you find is a snapshot somebody took once and never revisited, which is why half of them still describe servers that no longer work. This page is maintained, carries the date it was last checked, and says plainly when we could not confirm something rather than guessing.
How to read the statuses
First-party means the company publishes and documents its own server. That is the only status that comes with any expectation of maintenance, and today it applies to very few apps.
Community means one or more servers exist on GitHub, built by people who do not work at the company. These often work well. They also break when the underlying API changes, and nobody is obliged to fix them.
Unconfirmed means we could not verify a first-party server when we last checked. It is an honest statement about our checking, not a claim that none exists.
What to look at before installing any community server
Commit activity in the last couple of months. A README that lists the exact tools the server exposes. A stated authentication model naming the scopes it needs. Those three signals separate a server that will work next month from one that already does not.
The pattern across the whole category
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 a task app partly on this basis, test the one write you care most about before you commit.
What LemTask offers today
No MCP server yet, and this page will not pretend one exists. Webhooks, Zapier, Make and Apple Shortcuts are live now. When an MCP connection ships and has been tested end to end, it appears in the table above like everything else, with the same status labels applied to us.