mstodo-bridge

Manage Microsoft To Do directly in Claude. An MCP server with zero-configuration setup; sign-in happens right in the conversation.

Installation

1. Install into Claude Code

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

-s user applies globally (available in all projects). Restart your Claude Code session after finishing.

2. Or write to an MCP config file

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 it the same way with npx -y mstodo-bridge as the stdio command. Save and restart the client.

3. Or start a web service

It does not need to be attached to a client; it can also run standalone as a service with an admin console:

npx mstodo-bridge --http        # 管理台 http://127.0.0.1:46377/admin

On first launch it prints an admin password and an MCP Bearer token (shown only once). Other clients can then connect remotely via http://<host>:46377/mcp (Bearer auth); see "Deployment" below for deploying to a server / Hugging Face Spaces.

Related MCP server: Remote MCP Entra ID Todo

Sign-in

Option 1: Inside Claude (recommended)

After restarting the client, just tell Claude:

Help me connect to Microsoft To Do

Claude will call the login tool and give you an authorization link → open it in a browser → consent with your Microsoft personal account → it automatically reconnects and completes. After that you can operate in natural language:

Show my lists · Add X to "Research & Academics", due Friday · Search tasks containing "paper" · Complete item 3

Option 2: Through the web admin console

npx mstodo-bridge --http --open

1. Open the admin console in a browser and sign in with the admin password printed at startup;

2. On the Microsoft To Do card, click "Connect account"; after completing authorization in the browser, it automatically redirects back;

3. In remote environments (browser and server are not on the same machine), after authorization it will jump to localhost and show an error — this is expected; just paste the full URL from the address bar into the "Complete connection" input box on the card.

Both methods produce exactly the same credentials (~/.mstodo-bridge), so feel free to mix them.

MCP tools (15)

Account & sign-in

Lists

Task reading

Task writing

Parameters marked with provider? can be omitted in single-account mode.

Deployment

PORT=7860 HOST=0.0.0.0 PUBLIC_BASE_URL=https://<user>-<space>.hf.space npx mstodo-bridge --http

Security

Credentials are kept only locally (~/.mstodo-bridge, permissions 0600); passwords and tokens are stored only as scrypt hashes with constant-time comparison; OAuth uses PKCE plus a one-time state throughout; the admin console has strict CSP and login rate limiting. When a refresh token becomes invalid, it is automatically cleared and you are guided to reconnect.

Development

git clone https://github.com/WNJXYK/MSTodo-Bridge && cd MSTodo-Bridge
npm install && npm run build && npm test

Issues and PRs are welcome at GitHub.

License

MIT