Name: Microsoft Todo
Author: jordanburke

Microsoft Todo MCP

Microsoft To Do via Graph — task lists, tasks, checklist items and reminders.

Grade A Local · stdio API key 16 tools v1.2.0 · 31 Oct 2026 MIT

No reviews yet by jordanburkenpm 3,551 Runs on your machine, nothing hosted

99/100

trust score

downloads a day

local

runs on your machine

downloads in 30d

What it does

Microsoft To Do via Graph — task lists, tasks, checklist items and reminders.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user microsoft-todo-mcp '--' npx -y microsoft-todo-mcp-server

# 2 — ask your agent for something these tools do
#   auth-status, get-task-lists, get-task-lists-organized and 13 more

Microsoft Todo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

jordanburke10 servers

9 categories

All 10 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Microsoft Todo as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user microsoft-todo-mcp '--' npx -y microsoft-todo-mcp-server

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take MS_TODO_ACCESS_TOKEN (Microsoft Graph access token. Must be set together with MS_TODO_REFRESH_TOKEN; `mstodo-config` emits both.), MS_TODO_REFRESH_TOKEN (Refresh token. Required alongside the access token, but note the env-token path does not renew: once the access token expires the server returns 401 until it is replaced.), CLIENT_ID (Azure AD application (client) ID. The server reads it to refresh tokens when the stored token file carries no credentials; `mstodo-setup` also uses it.), CLIENT_SECRET (Azure AD client secret, used for the same token refresh and by `mstodo-setup`.), TENANT_ID (Azure AD tenant: 'organizations' (the default), 'consumers', 'common', or a tenant GUID.) if you want to set them.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Check if you're authenticated with Microsoft Graph API. Shows current token status and expiration time, and indicates if the token needs to be refreshed.

No parameter schema on file.

Get all Microsoft Todo task lists (the top-level containers that organize your tasks). Shows list names, IDs, and indicates default or shared lists.

No parameter schema on file.

Get all task lists organized into logical folders/categories based on naming patterns, emoji prefixes, and sharing status. Provides a hierarchical view similar to folder organization.

Parameter	Type	Required	Notes
includeIds	boolean	no	Include list IDs in output (default: false)
groupBy	string	no	Grouping strategy - 'category' (default), 'shared', or 'type'

Create a new task list (top-level container) in Microsoft Todo to help organize your tasks into categories or projects.

Parameter	Type	Required	Notes
displayName	string	yes	Name of the new task list

Update the name of an existing task list (top-level container) in Microsoft Todo.

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list to update
displayName	string	yes	New name for the task list

Delete a task list (top-level container) from Microsoft Todo. This will remove the list and all tasks within it.

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list to delete

Get tasks from a specific Microsoft Todo list. These are the main todo items that can contain checklist items (subtasks).

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list
filter	string	no	OData $filter query (e.g., 'status eq \'completed\'')
select	string	no	Comma-separated list of properties to include (e.g., 'id,title,status')
orderby	string	no	Property to sort by (e.g., 'createdDateTime desc')
top	number	no	Maximum number of tasks to retrieve
skip	number	no	Number of tasks to skip
count	boolean	no	Whether to include a count of tasks

Create a new task in a specific Microsoft Todo list. A task is the main todo item that can have a title, description, due date, and other properties.

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list
title	string	yes	Title of the task
body	string	no	Description or body content of the task
dueDateTime	string	no	Due date in ISO format (e.g., 2023-12-31T23:59:59Z)
startDateTime	string	no	Start date in ISO format (e.g., 2023-12-31T23:59:59Z)
importance	string	no	Task importance
isReminderOn	boolean	no	Whether to enable reminder for this task
reminderDateTime	string	no	Reminder date and time in ISO format
status	string	no	Status of the task
categories	array	no	Categories associated with the task

Update an existing task in Microsoft Todo. Allows changing any properties of the task including title, due date, importance, etc.

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list
taskId	string	yes	ID of the task to update
title	string	no	New title of the task
body	string	no	New description or body content of the task
dueDateTime	string	no	New due date in ISO format (e.g., 2023-12-31T23:59:59Z)
startDateTime	string	no	New start date in ISO format (e.g., 2023-12-31T23:59:59Z)
importance	string	no	New task importance
isReminderOn	boolean	no	Whether to enable reminder for this task
reminderDateTime	string	no	New reminder date and time in ISO format
status	string	no	New status of the task
categories	array	no	New categories associated with the task

Delete a task from a Microsoft Todo list. This will remove the task and all its checklist items (subtasks).

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list
taskId	string	yes	ID of the task to delete

Get checklist items (subtasks) for a specific task. Checklist items are smaller steps or components that belong to a parent task.

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list
taskId	string	yes	ID of the task

Create a new checklist item (subtask) for a task. Checklist items help break down a task into smaller, manageable steps.

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list
taskId	string	yes	ID of the task
displayName	string	yes	Text content of the checklist item
isChecked	boolean	no	Whether the item is checked off

Update an existing checklist item (subtask). Allows changing the text content or completion status of the subtask.

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list
taskId	string	yes	ID of the task
checklistItemId	string	yes	ID of the checklist item to update
displayName	string	no	New text content of the checklist item
isChecked	boolean	no	Whether the item is checked off

Delete a checklist item (subtask) from a task. This removes just the specific subtask, not the parent task.

Parameter	Type	Required	Notes
listId	string	yes	ID of the task list
taskId	string	yes	ID of the task
checklistItemId	string	yes	ID of the checklist item to delete

Move completed tasks older than a specified number of days from one list to another (archive) list. Useful for cleaning up active lists while preserving historical tasks.

Parameter	Type	Required	Notes
sourceListId	string	yes	ID of the source list to archive tasks from
targetListId	string	yes	ID of the target archive list
olderThanDays	number	no	Archive tasks completed more than this many days ago (default: 90)
dryRun	boolean	no	If true, only preview what would be archived without making changes

Test various Graph API queries to discover hidden properties or endpoints for folder/group organization in Microsoft To Do.

Parameter	Type	Required	Notes
testType	string	yes	Type of test to run

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Microsoft Todo or to call it, at any volume.

ATrust score 99 / 100

Release 1.2.0 · scanned 31 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score99

Client score99

Findings2 threat · 0 capability

Capabilityminimal

Coveragesource

Verificationsource

Surface digest3dc42bb9a3c6b1f1beb0abd46b9b206141397ac1d5a7e1d3b4c102e98f021b42

Score vectorthreat 99 → client 99

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
verification-discount	source	publisher verification (provenance) — cryptographic build provenance ties the artifact to its source	−0
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (16 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
auth-status	no tags
get-task-lists	no tags
get-task-lists-organized	no tags
create-task-list	no tags
update-task-list	no tags
delete-task-list	no tags
get-tasks	no tags
create-task	no tags
update-task	no tags
delete-task	no tags
get-checklist-items	no tags
create-checklist-item	no tags
update-checklist-item	no tags
delete-checklist-item	no tags
archive-completed-tasks	no tags
test-graph-api-exploration	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest3dc42bb9a3c6b1f1

Scanned2026-10-31

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.