Microsoft To Do MCP
Related Servers
Alternatives to Microsoft To Do MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude to create, read, update and delete Microsoft To Do lists, tasks and checklist items, and Microsoft Planner plans, buckets and tasks, through Microsoft Graph as the signed-in user. Lists, plans and buckets can be referenced by ID or exact name, with destructive deletes requiring confirmation.MIT
- AlicenseAqualityBmaintenanceConnects Microsoft To Do to Claude, enabling task fetching, planning, completion, note-taking, and checklist management through natural language.9MIT
- AlicenseAqualityAmaintenanceEnables AI agents to read and edit Microsoft To Do tasks, lists, and steps via Microsoft Graph, including due dates, reminders, and subtasks.121MIT
- AlicenseAqualityCmaintenanceEnables AI clients like Claude to read and manage Microsoft To Do task lists and tasks via the Microsoft Graph API, running locally over stdio with secure token storage.10152 npmMIT
- 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.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Microsoft To Do tasks via the Graph API, supporting multiple accounts, encrypted auth, and full CRUD operations.9 npm2MIT
TDQS
Scored across 18 tools
Most tools target distinct resources or actions, but the 'today' tools (get_today_tasks, get_my_day, add_today_task) and add_task vs add_today_task can be confused. Descriptions clarify the differences, so misselection is limited.
Nearly all tools use snake_case with a verb_noun pattern (list_tasks, add_step, update_task), which is predictable. Minor deviations like auth_status (noun_noun) and login (bare verb) are readable but not perfectly consistent.
18 tools is on the heavy side for a To Do client; several granular step tools and separate complete/uncomplete could be consolidated. The count is borderline but not excessive for the domain's sub-resources.
Task and step lifecycles are well covered, but list lifecycle is incomplete: create_list and list_lists exist with no update_list or delete_list. There is also no get_task for single-task detail retrieval, leaving notable gaps.