Microsoft Planner MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-tasksC | List all tasks in a Planner plan |
| get-taskC | Get details of a specific Planner task |
| get-task-detailsC | Get extended task details including description and checklist |
| create-taskC | Create a new task in a Planner plan |
| update-taskC | Update task properties (title, progress, assignments, categories). Auto-fetches ETag. |
| update-task-detailsA | Update task description (use for GitHub links). Auto-fetches ETag. |
| delete-taskB | Delete a Planner task. Auto-fetches ETag. |
| list-bucketsC | List all buckets in a Planner plan |
| list-plansB | List all Planner plans accessible to the current user |
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 9 tools
Most tools are clearly distinct, but 'get-task' and 'get-task-details' could cause confusion as they both retrieve task information. The descriptions help clarify that one gets basic details and the other extended details, but an agent might initially misselect between them.
All tool names follow a consistent verb_noun pattern with hyphens (e.g., create-task, list-tasks). The naming is predictable and readable throughout the set, with no deviations in style.
With 9 tools, this server is well-scoped for managing Microsoft Planner tasks and plans. Each tool serves a clear purpose, such as CRUD operations for tasks and listing plans/buckets, making the count appropriate for the domain.
The tool set provides strong coverage for task management, including create, read, update, and delete operations, plus listing plans and buckets. A minor gap is the lack of tools for managing buckets or plans beyond listing, but agents can still handle core workflows effectively.