mcp-planner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MS_CLIENT_ID | No | The Entra ID client (application) ID. | |
| MS_TENANT_ID | No | The Entra ID tenant ID. | |
| MS_CLIENT_SECRET | No | The client secret for app-only authentication. | |
| MS_REFRESH_TOKEN | No | A refresh token for delegated user authentication (alternative to MS_CLIENT_SECRET). | |
| PLANNER_ADVANCED_TOOLSET | No | Set to 'true' to enable the advanced toolset (graph_find_endpoint and graph_get). Defaults to 'false'. | false |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| planner_search_groupsA | Search Microsoft 365 groups (Teams) by display name. Use this first to find the group ID required by planner_list_plans. |
| planner_find_userA | Find a user by display name or UPN/email to get the user ID needed for task assignments and planner_list_user_tasks. |
| planner_list_plansA | List all Planner plans owned by a Microsoft 365 group. Get the group ID from planner_search_groups. |
| planner_get_planA | Get a Planner plan and its buckets. Bucket IDs are needed to create or move tasks. |
| planner_create_bucketA | Create a new bucket (column) in a plan. |
| planner_list_tasksA | List Planner tasks in a plan (or a single bucket). Optionally filter by assignee user ID or open/completed state. |
| planner_list_user_tasksA | List all Planner tasks assigned to a user across every plan they participate in. Get the user ID from planner_find_user. |
| planner_get_taskA | Get a Planner task including its description and checklist. Also returns the etags needed by update tools (updates fetch them automatically). |
| planner_create_taskA | Create a Planner task in a plan. Optionally set the bucket, due date, priority, assignees, and a description. |
| planner_update_taskA | Update a Planner task: title, bucket (move), due date, priority, progress (not started / in progress / completed), or assignees. Fetches the current etag automatically. |
| planner_update_task_detailsA | Update a task's description, add checklist items, or check/uncheck existing checklist items (item IDs come from planner_get_task). |
| planner_delete_taskA | Permanently delete a Planner task. This cannot be undone. |
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 12 tools
Each tool targets a distinct resource and action. The only potential overlap between planner_list_tasks and planner_list_user_tasks is clearly separated by scope: one lists tasks within a plan/bucket, the other lists all tasks across plans for a user.
All tool names follow a consistent verb_noun pattern in snake_case (search_groups, list_plans, create_bucket, update_task_details, etc.). No mixed conventions or vague verbs.
12 tools is well-scoped for a Microsoft Planner server, covering discovery (groups, users), plan/bucket inspection, and full task lifecycle (list, get, create, update, delete) without bloat.
The task lifecycle is fully covered (create, read, update, delete, plus details updates). Minor gaps exist such as no update/delete bucket or plan creation, but these are secondary to the core Planner workflows and often outside the intended scope.