A
licenseNot graded
qualityC
maintenanceEnables managing Microsoft To Do lists and tasks through MCP, including creating, updating, completing, deleting, searching, and checklist operations via Microsoft Graph.
MIT
Microsoft To Do MCP
by jordanburke
Related Servers
Alternatives to Microsoft To Do MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to read and edit Microsoft To Do tasks, lists, and steps via Microsoft Graph, including due dates, reminders, and subtasks.121MIT
- AlicenseAqualityCmaintenanceConnects Microsoft To Do to Claude, enabling task fetching, planning, completion, note-taking, and checklist management through natural language.9MIT
- AlicenseAqualityBmaintenanceMCP server for Microsoft To Do that enables managing task lists, tasks, and checklist items via the Microsoft Graph API with zero-config authentication.132Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables comprehensive Microsoft To Do task management through Microsoft Graph API with Entra ID OAuth authentication. Supports creating, updating, and managing todo lists, tasks, reminders, and due dates through natural language.-
- AlicenseBqualityCmaintenanceLets Claude and other AI clients read and modify Microsoft To Do through natural language, adding, completing, searching, updating, and deleting tasks and sub-steps by title and list name instead of ids. Personal Microsoft accounts need no Azure app registration — a single device-code sign-in grants access, with optional read-only and no-delete modes available.18MIT
TDQS
A3.7/5.0
Scored across 16 tools
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count4/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessOutdated data