Microsoft To Do MCP
Microsoft To Do MCP gives an agent tasks with checklist items and recurrence rules for working on the user’s own plans.
- 120 ★ on the repository
- Last commit
Extended access
Why this level
- The agent can create and modify tasks and lists within delegated account permissions.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/microsoft-to-do-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent can create and modify tasks and lists within delegated account permissions.
This is third-party code. Review the repository files before installing.
What it does
Microsoft To Do MCP connects an agent to the user’s lists and tasks through Microsoft Graph. After sign-in, the agent reads lists, creates and updates tasks, completes checklist items within a task and sets recurrence. Actions use the account owner’s delegated permissions. A local server needs an Azure app registration and OAuth setup. Tokens are stored in a user directory and refreshed when app credentials are available. The mstodo-config command prepares MCP client settings after authentication.
Who it is for. Microsoft To Do users reviewing and updating their own tasks through Claude or Cursor.
Good fit when
- A user reviews a task list and identifies next actions.
- An agent creates Microsoft To Do tasks from an approved plan.
- A user sets a recurrence schedule for a regular task.
- Checklist items are completed as work on a task progresses.
Not a fit when
- You cannot register an app or retain local OAuth tokens.
- The agent must not change tasks on the owner’s behalf.
- You need operation without a Microsoft account or Graph permissions.
Example request
Read my Microsoft To Do lists and propose a daily plan without creating or completing tasks.MCP
- Transport
- stdio
- Authentication
- OAuth
Limitations
Self-hosting requires Azure app registration, client credentials and Microsoft Graph permissions. Tenant configuration controls supported account types, so align it with personal or work login. Token renewal needs the app’s client ID and secret; supplied tokens alone stop working after expiration. Token files and generated MCP configuration can contain task access credentials, so keep them outside Git and restrict read permissions.
How to disable. Remove the client entry and stop the process. Revoke Microsoft app consent and delete retained tokens when no longer needed.
FAQ
Are personal Microsoft accounts supported?
Yes. Enable personal accounts when registering the Azure app. Set TENANT_ID to `consumers` for personal accounts or `common` for personal and work accounts. Follow the [Azure setup](https://github.com/jordanburke/microsoft-todo-mcp-server#azure-app-registration).
Where are tokens stored?
Usually in `~/.config/microsoft-todo-mcp/tokens.json`; override with `MSTODO_TOKEN_FILE` and check permissions.
Are recurring tasks supported?
Yes through Microsoft Graph recurrence rules. Confirm the schedule before creation.
Why is CLIENT_SECRET needed?
Among other things, it enables token refresh. Keep it outside public configuration.
How do I generate client configuration?
Use `mstodo-config` after authentication and inspect the output without publishing tokens.
Discussion
No questions or reviews yet.
Related
MCP serversThe official Todoist MCP server: the agent finds, creates and updates tasks and projects in your account
An MCP server for Todoist: Claude creates, finds, edits, completes and deletes tasks from an ordinary phrase, with five tools
An MCP server that gives the agent access to mail, calendar, OneDrive files and Power Automate flows through Microsoft Graph
Things MCP: Things 3 tasks for an agent
Things MCP Server
An MCP server for Things 3 on Mac: Claude reads lists, searches tasks and creates or updates them, including in bulk.
19 Todoist tools for Claude: tasks, subtasks, projects, labels and reminders, bulk edits and a dry-run mode.
The MCP server of the local Taskdog task manager: an agent creates tasks, runs their lifecycle and splits big ones into subtasks.
README in short
Legacy working-directory tokens migrate to user storage on read. Environment token pairs seed a session; refreshed tokens are saved to the file.