Microsoft To Do MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLIENT_ID | No | Azure App Registration client ID, required for authentication and for token renewal. | |
| TENANT_ID | No | Tenant setting: 'organizations' (multi-tenant organizational, default), 'consumers' (personal accounts), 'common' (both), or a specific tenant ID. | |
| REDIRECT_URI | No | OAuth redirect URI, must match the Azure app registration (e.g. http://localhost:3000/callback). | |
| CLIENT_SECRET | No | Azure App Registration client secret, required for authentication and for token renewal. | |
| MSTODO_TOKEN_FILE | No | Override path to a custom tokens.json file. Defaults to the per-user config directory, then tokens.json in the working directory. | |
| MS_TODO_ACCESS_TOKEN | No | Supply an access token directly, which takes precedence over the token file. | |
| MS_TODO_REFRESH_TOKEN | No | Supply a refresh token directly, which takes precedence over the token file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth-statusA | 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. |
| get-task-listsA | Get all Microsoft Todo task lists (the top-level containers that organize your tasks). Shows list names, IDs, and indicates default or shared lists. |
| get-task-lists-organizedA | 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. |
| create-task-listA | Create a new task list (top-level container) in Microsoft Todo to help organize your tasks into categories or projects. |
| update-task-listA | Update the name of an existing task list (top-level container) in Microsoft Todo. |
| delete-task-listA | Delete a task list (top-level container) from Microsoft Todo. This will remove the list and all tasks within it. |
| get-tasksB | Get tasks from a specific Microsoft Todo list. These are the main todo items that can contain checklist items (subtasks). |
| create-taskB | 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. Pass |
| update-taskA | Update an existing task in Microsoft Todo. Allows changing any properties of the task including title, due date, importance, and recurrence. To stop a recurring task, pass |
| delete-taskA | Delete a task from a Microsoft Todo list. This will remove the task and all its checklist items (subtasks). |
| get-checklist-itemsA | Get checklist items (subtasks) for a specific task. Checklist items are smaller steps or components that belong to a parent task. |
| create-checklist-itemA | Create a new checklist item (subtask) for a task. Checklist items help break down a task into smaller, manageable steps. |
| update-checklist-itemA | Update an existing checklist item (subtask). Allows changing the text content or completion status of the subtask. |
| delete-checklist-itemA | Delete a checklist item (subtask) from a task. This removes just the specific subtask, not the parent task. |
| archive-completed-tasksA | 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. |
| test-graph-api-explorationA | Test various Graph API queries to discover hidden properties or endpoints for folder/group organization in Microsoft To Do. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools map clearly to distinct resources and CRUD actions (task lists, tasks, checklist items), so selection is generally straightforward. The main ambiguity is between get-task-lists and get-task-lists-organized, plus the diagnostic-sounding test-graph-api-exploration, which could be confused with normal retrieval or discovery workflows.
Names are consistently kebab-case and mostly follow a verb_noun pattern (create-task, update-checklist-item, delete-task-list). Exceptions like auth-status and test-graph-api-exploration slightly break the verb-first convention but remain readable and predictable.
At 16 tools, the set is slightly above the ideal compact range but still reasonable for covering lists, tasks, and checklist items with full CRUD. A couple of extras (organized list view and Graph API exploration) inflate the count without being core day-to-day operations.
The server covers full create/get/update/delete lifecycles for task lists, tasks, and checklist items, plus authentication status and an archive workflow. Minor gaps remain, such as no dedicated single-resource getters or explicit move-task-between-lists operation, but agents can work around these with existing tools.