The AI assistant translates your request into the appropriate tool calls automatically.
The AI assistant translates your request into the appropriate tool calls automatically. The microsoft planner mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
Tasks.ReadWrite — read and write Planner tasksUser.Read — read the signed-in user's profileUser.ReadBasic.All — resolve user display names from the GUIDs in task assignments (required only for list_users tool)Local — The MCP endpoint is available at http://localhost:8000/mcp. A health check endpoint is at http://localhost:8000/healthUser — The User tool exposed by this serverget_me — Return the authenticated user's profile from Microsoft Graphlist_users — Retrieve Microsoft 365 users by GUID, e-mail address, or free-text search. Useful for resolving the user GUIDs returned in task assignment objects toGroups — The Groups tool exposed by this serverlist_my_groups — List all Microsoft 365 groups the authenticated user is a member ofPlans — The Plans tool exposed by this serverlist_my_plans — The list_my_plans tool exposed by this serverlist_group_plans — The list_group_plans tool exposed by this serverYou will need 7 environment variables: OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_SERVICE_NAME, CLIENT_ID, CLIENT_SECRET, TENANT_ID, BASE_URL, MCP_PROXY_AUTH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Microsoft Planner MCP's toolset — Tasks.ReadWrite, User.Read, User.ReadBasic.All and 11 more — is a fair guide to whether it matches your workflow. It is maintained by aixolotl; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Tasks.ReadWrite | read and write Planner tasks |
| User.Read | read the signed-in user's profile |
| User.ReadBasic.All | resolve user display names from the GUIDs in task assignments (required only for list_users tool) |
| Local | The MCP endpoint is available at http://localhost:8000/mcp. A health check endpoint is at http://localhost:8000/health. |
| User | The User tool exposed by this server. |
| get_me | Return the authenticated user's profile from Microsoft Graph. |
| list_users | Retrieve Microsoft 365 users by GUID, e-mail address, or free-text search. Useful for resolving the user GUIDs returned in task assignment objects to display names. |
| Groups | The Groups tool exposed by this server. |
| list_my_groups | List all Microsoft 365 groups the authenticated user is a member of. |
| Plans | The Plans tool exposed by this server. |
| list_my_plans | The list_my_plans tool exposed by this server. |
| list_group_plans | The list_group_plans tool exposed by this server. |
| create_plan | The create_plan tool exposed by this server. |
| delete_plan | The delete_plan tool exposed by this server. |
{
"mcpServers": {
"microsoft-planner": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"OTEL_EXPORTER_OTLP_ENDPOINT": "your-value",
"OTEL_SERVICE_NAME": "your-value",
"CLIENT_ID": "your-value",
"CLIENT_SECRET": "your-value",
"TENANT_ID": "your-value",
"BASE_URL": "your-value",
"MCP_PROXY_AUTH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OTEL_EXPORTER_OTLP_ENDPOINT | Configuration value read at startup. | Optional |
| OTEL_SERVICE_NAME | Configuration value read at startup. | Optional |
| CLIENT_ID | Configuration value read at startup. | Optional |
| CLIENT_SECRET | Credential the server authenticates with. | Yes |
| TENANT_ID | Configuration value read at startup. | Optional |
| BASE_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_PROXY_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.