MCP Microsoft Todo

What MAG-Cie/mcp-microsoft-todo MCP server does

MAG-Cie/mcp-microsoft-todo MCP server exposes Microsoft To Do operations as MCP tools. It can enumerate lists, read individual tasks, create and edit tasks, mark tasks complete, delete them, and move them between lists. Task creation and updates support fields such as title, status, due dates, importance, recurrence, reminders, and categories.

The server also covers task organization and reporting. Agents can search titles across all lists, summarize items due today or already overdue, retrieve every active task in one operation, filter tasks by category, and list overdue tasks. Checklist items, linked resources, and Microsoft Graph open extensions are managed through separate tools. An iCalendar export produces VTODO data for use with calendar and task applications named in the project documentation, including Google Calendar, Apple Calendar, Outlook, and Thunderbird.

How it works

The server uses Microsoft Graph and authenticates through MSAL device code flow. A user opens the displayed Microsoft sign-in URL, enters the supplied code, and grants access with their Microsoft account. No client secret or Azure setup is required for normal use. The account can be personal, Microsoft 365, or Office 365.

After authentication, the token cache is saved at ~/.mcp-microsoft-todo/token-cache.json and refreshed automatically. Most operations run against the relevant To Do list or task. Several higher-volume operations use Graph batching: listing all tasks uses $batch, while batch creation, completion, and deletion accept up to 100 items and split requests into groups of 20. Moving a task recreates it in the destination list and removes the source task, so its ID changes and checklist items or linked resources are not transferred.

Setup and configuration

MAG-Cie/mcp-microsoft-todo MCP server requires Node.js 20 or newer and a Microsoft account. Install it as a stdio MCP server with npx -y @mag-cie/mcp-microsoft-todo, using the configuration format required by the selected client.

For personal Microsoft accounts, set MS_TENANT=consumers. The README recommends running the package with --auth once in a terminal so the device code is visible immediately; clients can also trigger authentication on the first tool call. MCP_LOCALE=fr optionally localizes compact-format strings. Developers using a fork may need MS_CLIENT_ID, but the official npm package does not require it.

Claude Code can register the server with claude mcp add --transport stdio. Claude Desktop uses an mcpServers entry with npx as the command. Cursor, Continue, and other stdio-capable clients can use the same command and arguments in their own configuration format.

Tools and capabilities

The documented tool set includes 28 operations for:

• Lists and tasks, including OData filters, ordering, pagination, recurrence, and reminders.
• Batch creation, completion, and deletion.
• Today, overdue, cross-list search, and category-based queries.
• Checklist items and linked resources.
• Custom JSON metadata through open extensions.
• Category updates across multiple tasks.
• iCalendar export with recurrence rules and alarms when conversion is possible.

Safety annotations distinguish read operations, updates, non-idempotent writes, and destructive deletes.

Limitations and notes

Title search is case-sensitive and excludes completed tasks by default. Bulk and all-list operations may apply active-task filters unless completed items are explicitly requested. Moving a task does not preserve checklist items or linked resources because of a Microsoft Graph limitation, and the recreated task receives a new ID. Deletion is permanent. If authentication fails, the documented recovery is to remove the local token-cache directory and sign in again; personal accounts may require MS_TENANT=consumers.