Microsoft Todo MCP Server

Microsoft Todo MCP service for Claude and Cursor. Fork of @jhirono/todomcp. Exposed over MCP by the microsoft todo mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol (MCP) server that enables AI assistants like Claude and Cursor to interact with Microsoft To Do via the Microsoft Graph API. This service provides comprehensive task management capabilities through a secure OAuth 2.0 authentication flow.

• 15 MCP Tools — Complete task management functionality including lists, tasks, checklist items, and organization features
• Seamless Authentication — Automatic token refresh with zero manual intervention
• OAuth 2.0 Authentication — Secure authentication with automatic token refresh
• Microsoft Graph API Integration — Direct integration with Microsoft's official API
• Multi-tenant Support — Works with personal, work, and school Microsoft accounts
• TypeScript — Fully typed for reliability and developer experience

Its toolset

Everything the assistant can do here goes through one of these:

• Authentication — The Authentication tool exposed by this server
• Debugging — The Debugging tool exposed by this server

Configuration

You will need 6 environment variables: MS_TODO_ACCESS_TOKEN, MS_TODO_REFRESH_TOKEN, MSTODO_TOKEN_FILE, CLIENT_ID, CLIENT_SECRET, TENANT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 16 or higher (tested with Node.js 18.x, 20.x, and 22.x) - pnpm package manager - A Microsoft account (personal, work, or school) - Azure App Registration (see setup below)

Adding it to your client

The server ships on npm as microsoft-todo-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Microsoft Todo's toolset — Authentication, Debugging — is a fair guide to whether it matches your workflow. It is maintained by jordanburke; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the microsoft todo mcp server does with a few real requests.