MCP server for Microsoft Tasks (Planner + To Do, unified) — read-only by default, writes opt-in, never modifies tasks the agent didn't create.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-server-microsoft-tasks","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<!-- SPDX-License-Identifier: MIT OR Apache-2.0 --> # mcp-server-microsoft-tasks [](https://pypi.org/project/mcp-server-microsoft-tasks/) [](https://github.com/XMV-Solutions-GmbH/microsoft-tasks-mcp/blob/main/LICENSE) [](https://github.com/XMV-Solutions-GmbH/microsoft-tasks-mcp/actions/workflows/ci.yml) [](https://github.com/XMV-Solutions-GmbH/microsoft-tasks-mcp/issues) > **In one sentence:** an [MCP](https://modelcontextprotocol.io) server that lets AI coding agents read your **Microsoft Planner + Microsoft To Do** tasks across all M365 tenants you sign into, without bypassing Microsoft's auth and without ever modifying tasks the agent didn't create itself. ## What is this for? You work across multiple Microsoft 365 tenants — consultancy, customer engagements, your own org. Tasks are scattered across: - **Microsoft To Do** — your personal task lists, the place flagged emails land, the place ad-hoc reminders go. - **Microsoft Planner** — group-scoped boards, one per M365 group / Team, where collaborative work lives. Surfacing "what do I have to do today" already requires the user to mentally union both surfaces. Worse, popular AI agents that *can* talk to Microsoft 365 either: - bypass Microsoft's modern auth (broken attribution), - can't see the multi-tenant boundary, - or auto-modify tasks created by other people (terrifying). `mcp-server-microsoft-tasks` fixes all three: **local process per tenant, multi-profile, Microsoft Graph for full attribution, read-only by default, writes opt-in (v0.2+), agent-created-only**. The per-profile registry is the hard gate — write tools refuse to touch any task whose ID isn't in the regist…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.