Planner MCP Server
Related Servers
Alternatives to Planner MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude clients to read and update Microsoft Planner tasks in group plans as the signed-in user, using Entra ID token validation and an On-Behalf-Of exchange for Microsoft Graph access.MIT
- AlicenseBqualityBmaintenanceEnables 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.31MIT
- FlicenseAqualityBmaintenanceEnables Claude to manage Outlook calendar events and Microsoft To Do tasks for a specific mailbox via Microsoft Graph API.7-
- AlicenseNot gradedqualityCmaintenanceEnables Claude to read, create, and complete tasks in a personal Microsoft To Do account through the Microsoft Graph API, including lists, daily and overdue tasks, due dates, reminders, notes, and checklist steps.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects Claude to Microsoft Outlook through the Microsoft Graph API, enabling email management (list, search, read, send) and calendar operations (list, create, accept, decline, delete events) via OAuth 2.0 authentication.1MIT
- AlicenseNot gradedqualityBmaintenanceConnects Claude with Microsoft 365 services such as Email, Calendar, Teams, OneDrive, and more through the Microsoft Graph API.45 npm17MIT
TDQS
Scored across 14 tools
Tools are generally distinct with clear purposes. There is slight overlap between get_plan and get_plan_details, but the latter includes category descriptions, reducing ambiguity. Other tools cover different resources (auth, user, plans, buckets, tasks) with no major confusion.
All tool names follow a consistent verb_noun pattern using underscores (e.g., create_task, list_buckets, get_plan). Auth tools use a verb_noun structure as well (auth_poll, auth_start). No mixing of conventions like camelCase.
14 tools cover the core functionality of a Planner server, including authentication, plans, buckets, tasks, user info, and group members. The count is well-scoped—not too many to overwhelm, yet sufficient for common operations.
Task CRUD is complete (create, read, update, delete), but bucket and plan operations are incomplete: missing create_plan, delete_plan, update_bucket, delete_bucket. No task assignment tool. These gaps may hinder some workflows.