Apple Reminders is the privacy outlier. There is no cloud API, so nothing here involves handing a token to a third party. MCP servers for Reminders drive the local app on macOS through scripting, which means your reminders never leave the machine — and also means this only works on a Mac, with the app present.
The permission prompt is the setup
The first time the server tries to drive Reminders, macOS asks whether the process may control the app. Grant it and everything works. Miss it, or dismiss it, and every call fails with a permission error that looks like a bug. If nothing works on first run, check System Settings under Privacy and Security, then Automation.
Speed, or the lack of it
Scripting the app is slower than an HTTP API. Creating one reminder is fine. Asking for a rewrite of forty is noticeably slow and sometimes stalls. Keep requests small.
Why it is still worth it
For anyone whose reminders are already on iPhone and Mac, this is the only route that adds an assistant without adding a cloud service. "Remind me about this tomorrow morning" from a chat window, landing on the phone in your pocket, with nothing synced to a vendor in between. That is a genuinely good trade.
Where LemTask stands today
LemTask does not ship an MCP server yet, and we are not going to pretend otherwise on a page developers will read. What LemTask has working right now is outbound and inbound webhooks, Zapier, Make and Apple Shortcuts, which covers "when a task is created, do X" and "create a task from anything that can send an HTTP request". An MCP connection is on the roadmap; when it ships and we have tested it end to end with Claude, this page will say so with the config block, and not a day earlier.