Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http microsoft-todo 'https://gateway.pipeworx.io/microsoft-todo/mcp'{
"mcpServers": {
"microsoft-todo": {
"type": "http",
"url": "https://gateway.pipeworx.io/microsoft-todo/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
mcp-microsoft-todo
Microsoft To Do (Microsoft 365) MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
list_task_lists | List the Microsoft To Do task lists for the signed-in user, with display names and whether each is a well-known list (e.g. the default "Tasks" or flagged-email list). Use to discover a to-do list and its ID before listing tasks or reminders. |
list_tasks | List the tasks in a Microsoft To Do list. Returns compact task summaries (title, status, importance, due date, created/completed times, and a body preview). Optionally filter by status. Use to browse a user's to-do list and see what tasks or reminders it contains. |
get_task | Get the full details of a single Microsoft To Do task by its list ID and task ID, including title, status, importance, full body/notes, due date, reminder time, created/completed times, and any checklist (sub-task) items. Use after list_tasks or find_due_tasks to read a to-do item in full. |
find_due_tasks | Find upcoming, incomplete Microsoft To Do tasks across all of the user's to-do lists that are due within the next N days. Returns a flat list of due reminders with their list name, title, due date, and importance. Use to answer "what tasks are due soon" or "what are my upcoming reminders". |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"microsoft-todo": {
"url": "https://gateway.pipeworx.io/microsoft-todo/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/microsoft-todo/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
This pack runs against a connected microsoft account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect microsoft, then call POST https://gateway.pipeworx.io/v1/tools/list_task_lists with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/list_task_lists. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"microsoft-todo": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-microsoft-todo"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-microsoft-todoIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Microsoft Todo data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Questions fréquentes
Qu'est-ce que Microsoft Todo ?
Microsoft To Do (Microsoft 365) MCP Pack
Comment installer Microsoft Todo ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http microsoft-todo 'https://gateway.pipeworx.io/microsoft-todo/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Microsoft Todo ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Microsoft Todo est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Microsoft Todo ?
Il est publié par pipeworx-io. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.