MCP for Microsoft To Do
Related Servers
Alternatives to MCP for Microsoft To Do
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityCmaintenanceAn MCP server to read and manage your Microsoft To Do tasks through the Microsoft Graph To Do API.MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for use with msgraph calls to mail, calendar, and files16MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants like Claude and Cursor to interact with Microsoft To Do via the Microsoft Graph API.57 npmMIT
- FlicenseNot gradedqualityCmaintenanceA self-hosted Model Context Protocol server for Microsoft To Do. The key problem this solves: the Microsoft Graph API silently omits user-created lists on personal accounts (GET /me/todo/lists only returns well-known lists like "Flagged Emails"). This server works around it with a local SQLite registry that tracks every list you create, so your lists always show up.5-
- AlicenseBqualityCmaintenanceA local MCP server that lets Codex and other MCP clients manage Microsoft To Do tasks through Microsoft Graph, supporting listing, creating, updating, and completing tasks.5MIT
TDQS
Scored across 28 tools
Each tool has a clearly distinct purpose, with names that directly indicate their function. Batch operations are clearly separated from single operations, and tools for different resources (tasks, checklist items, linked resources, extensions) are easily distinguishable.
Tool names consistently follow a verb_noun pattern with underscores, using lowercase. Prefixes like batch_, list_, create_, delete_, update_ are used predictably, making the naming scheme intuitive and easy to navigate.
With 28 tools, the server covers a comprehensive set of operations for Microsoft To Do, including batch operations and exports. While a bit on the higher side, the count is justifiable given the domain's complexity and the need to support multiple resource types.
The tool set covers nearly all core workflows: CRUD for tasks, checklist items, linked resources, and extensions; batch operations; search; export; and summary. Minor gaps include the absence of tools to create, update, or delete task lists themselves.