Microsoft Planner runs on your own machine — the client starts it, so there is no endpoint to ping. 103 installs a week from npm. Last commit 31 Aug 2026.
Microsoft Planner MCP server — plans, buckets, tasks via Microsoft Graph, ETags handled
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет mcp-planner ссылается на mspstack/mcp-planner
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-planner -e 'MS_TENANT_ID=<MS_TENANT_ID>' -e 'MS_CLIENT_ID=<MS_CLIENT_ID>' -e 'MS_CLIENT_SECRET=<MS_CLIENT_SECRET>' -- npx -y mcp-planner
{
"mcpServers": {
"mcp-planner": {
"command": "npx",
"args": [
"-y",
"mcp-planner"
],
"env": {
"MS_CLIENT_ID": "<MS_CLIENT_ID>",
"MS_CLIENT_SECRET": "<MS_CLIENT_SECRET>",
"MS_TENANT_ID": "<MS_TENANT_ID>"
}
}
}
}
[mcp_servers.mcp-planner]
command = "npx"
args = ["-y", "mcp-planner"]
env = { MS_TENANT_ID = "<MS_TENANT_ID>", MS_CLIENT_ID = "<MS_CLIENT_ID>", MS_CLIENT_SECRET = "<MS_CLIENT_SECRET>" }
{
"mcpServers": {
"mcp-planner": {
"command": "npx",
"args": [
"-y",
"mcp-planner"
],
"env": {
"MS_CLIENT_ID": "<MS_CLIENT_ID>",
"MS_CLIENT_SECRET": "<MS_CLIENT_SECRET>",
"MS_TENANT_ID": "<MS_TENANT_ID>"
}
}
}
}
{
"servers": {
"mcp-planner": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-planner"
],
"env": {
"MS_CLIENT_ID": "<MS_CLIENT_ID>",
"MS_CLIENT_SECRET": "<MS_CLIENT_SECRET>",
"MS_TENANT_ID": "<MS_TENANT_ID>"
}
}
}
}
Put your own values in place of
<MS_TENANT_ID> (Microsoft Entra ID tenant id (GUID or domain)), <MS_CLIENT_ID> (Entra app registration client id), <MS_CLIENT_SECRET> (Entra app registration client secret (app needs Tasks.ReadWrite.All, GroupMember.Read.All, User.Read.All application permissions)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
PLANNER_ADVANCED_TOOLSET (true/1 registers the advanced toolset (graph_get, graph_find_endpoint) — a read-only escape hatch limited to /planner, /groups, /users).
Microsoft Planner MCP server — plans, buckets, tasks via Microsoft Graph, ETags handled
Microsoft Planner MCP: create tasks and buckets, list plans and tasks, complete tasks.
Microsoft Calendar (Outlook Calendar) MCP server for managing events via Microsoft Graph.
MCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API.
MCP server for Outlook personal accounts (Hotmail/Outlook.com) via Microsoft Graph API
Microsoft Outlook MCP server — 20 tools for email, calendar, contacts, and settings via Graph API.
Microsoft Outlook (mail) MCP server — read, search, and send email through Microsoft Graph.
MCP server for Microsoft To Do via Microsoft Graph. MSAL device code flow, no client secret needed.
Answers built from our own checks of this server.