Microsoft TODO Bridge

Manage your Microsoft To Do from Claude. A local MCP server — sign-in happens inside the chat.

English | 简体中文

📦 Install

Claude Code — one line, all projects:

claude mcp add -s user taskbridge -- npx -y mstodo-bridge

Claude Desktop — edit the config file (Windows %APPDATA%\Claude\claude_desktop_config.json, macOS ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "taskbridge": {
      "command": "npx",
      "args": ["-y", "mstodo-bridge"]
    }
  }
}

Cursor / other MCP clients — add npx -y mstodo-bridge as a stdio command. Restart the client.

That is the whole install. Everything runs locally; the only files written are your credentials in ~/.mstodo-bridge.

Related MCP server: Remote MCP Entra ID Todo

🔑 Sign in

Just say:

Connect my Microsoft To Do

Claude calls the login tool and hands you a link → open it → consent with your personal Microsoft account → done. Tokens refresh automatically. Then talk naturally:

Show my lists · Add X to “Research”, due Friday · Find tasks mentioning “paper” · Complete #3

Running the MCP server on a remote host? The consent redirect lands on your machine's localhost and shows an error page — expected. Copy that address-bar URL into the chat; Claude calls login with it to finish. No console, no tokens to copy.

🧰 Tools (15)

⚙️ Configuration

🔒 Security

Credentials stay local (~/.mstodo-bridge, mode 0600). The OAuth client is a public client — no secret ships in the package (same model as VS Code / Azure CLI). Sign-in uses PKCE (S256) with one-time state; expired refresh tokens are wiped and flagged for re-login. logout removes local tokens; Microsoft-side consent is revoked at account.microsoft.com.

License

MIT