codex-microsoft-todo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MS_TODO_CLIENT_ID | Yes | The Application (client) ID of your Microsoft Entra app registration. Used for device-code authentication with Microsoft Graph. |
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 |
|---|---|
| list_task_listsA | 列出当前 Microsoft To Do 的任务列表 |
| list_tasksC | 列出一个 To Do 列表中的任务 |
| create_taskB | 在 Microsoft To Do 中创建任务 |
| update_taskC | 修改 Microsoft To Do 任务的标题、正文、重要性、截止时间或提醒 |
| complete_taskB | 将 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 5 tools
Each tool targets a distinct resource and action: task lists vs. tasks, and separate create/update/complete operations. There is no meaningful overlap between the tool purposes.
All tool names follow a consistent verb_noun snake_case pattern: list_task_lists, list_tasks, create_task, update_task, complete_task. The naming clearly indicates both the action and the resource.
With 5 tools, the server is well-scoped for a focused Microsoft To Do integration. Each tool covers a core operation without unnecessary bloat.
The core workflow of listing, creating, updating, and completing tasks is covered, but there is no delete_task or ability to create/rename task lists. The lack of delete capability is a notable gap in lifecycle management.