Microsoft To Do MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MS_TODO_CLIENT_ID | Yes | Your Azure AD application (client) ID for the Microsoft To Do MCP server. |
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 |
|---|---|
| todo_list_task_listsA | List all Microsoft To Do task lists for the signed-in user (e.g. 'Tasks', 'Groceries'). Returns each list's display name and id. Use the id with todo_list_tasks to see tasks inside a list. |
| todo_create_task_listA | Create a new Microsoft To Do task list with the given display name. Returns the new list's id. |
| todo_rename_task_listA | Rename an existing Microsoft To Do task list. |
| todo_delete_task_listA | Permanently delete a Microsoft To Do task list AND all tasks inside it. This cannot be undone. Confirm with the user before calling this. |
| todo_list_tasksA | List tasks inside a given Microsoft To Do list. Supports filtering by status. Get list_id from todo_list_task_lists first. |
| todo_get_taskA | Get full details of a single task, including its notes. |
| todo_create_taskA | Create a new task in a given Microsoft To Do list. Get list_id from todo_list_task_lists first. |
| todo_update_taskA | Update fields on an existing task (title, notes, due date, importance, or status). Only the fields you provide are changed. To mark a task done, prefer todo_complete_task. |
| todo_complete_taskA | Mark a task as completed (shortcut for todo_update_task with status=completed). |
| todo_delete_taskA | Permanently delete a task. This cannot be undone. Confirm with the user before calling this. |
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 10 tools
Each tool targets a distinct resource and action: task lists vs. tasks, and operations like list, create, rename, delete, get, update, complete are clearly separated. The only potential overlap is todo_complete_task being a shortcut for todo_update_task, but the description explicitly clarifies this.
All tool names follow a consistent todo_verb_noun pattern, with verbs like list, create, rename, delete, get, update, complete applied uniformly to the two resources (task lists and tasks). This makes the API predictable and easy to navigate.
10 tools is well-scoped for a Microsoft To Do server, covering both task list management and task management without unnecessary bloat. Each tool serves a clear, distinct purpose and earns its place.
The server provides full CRUD coverage for task lists (list, create, rename, delete) and tasks (list, get, create, update, complete, delete), covering the core lifecycle. The complete_task shortcut is a sensible addition for a common operation.