Microsoft To Do is not really a standalone target: everything goes through Microsoft Graph, which means the deciding factor is your account type, not the MCP server you choose. On a personal Microsoft account this is straightforward. On a work or school account, your tenant administrator decides whether it happens at all.
Admin consent is the actual blocker
Graph permissions for tasks frequently need administrator consent on managed tenants. If you are on a work account and the authorisation screen ends in a message about needing approval, no amount of config editing will fix it. That is a conversation with IT, and it is a reasonable thing for them to be careful about.
Permissions that fail quietly
Graph has both delegated and application permissions, and closely named scopes with different reach. The failure mode is not an error, it is an empty list — the assistant says you have no tasks and sounds certain. If reads come back empty on an account you know has tasks, suspect the scope before the server.
Where it shines
Flagged email. Outlook turns flagged messages into To Do items, and an assistant that can read that list turns "what did I flag this week and is any of it still open" into one question. That alone justifies the setup for people who live in Outlook.
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.