Microsoft To Do MCP

A Model Context Protocol (MCP) server that enables AI assistants like Claude and Cursor to interact with Microsoft To Do via the Microsoft Graph API. This service provides comprehensive task management capabilities through a secure OAuth 2.0 authentication flow.

Features

• 15 MCP Tools: Complete task management functionality including lists, tasks, checklist items, and organization features
• Seamless Authentication: Automatic token refresh with zero manual intervention
• OAuth 2.0 Authentication: Secure authentication with automatic token refresh
• Microsoft Graph API Integration: Direct integration with Microsoft's official API
• Multi-tenant Support: Works with personal, work, and school Microsoft accounts
• TypeScript: Fully typed for reliability and developer experience
• ESM Modules: Modern JavaScript module system

Prerequisites

• Node.js 16 or higher (tested with Node.js 18.x, 20.x, and 22.x)
• pnpm package manager
• A Microsoft account (personal, work, or school)
• Azure App Registration (see setup below)

Installation

Option 1: Global Installation (Recommended)

# Install globally using npm
npm install -g microsoft-todo-mcp-server

# Or using pnpm
pnpm install -g microsoft-todo-mcp-server

# Or run directly with npx (no installation)
npx microsoft-todo-mcp-server

The package provides three command aliases:

• microsoft-todo-mcp-server - Full package name
• mstodo - Short alias for the MCP server
• mstodo-config - Configuration helper tool

Option 2: Clone and Run Locally

git clone https://github.com/jordanburke/microsoft-todo-mcp-server.git
cd microsoft-todo-mcp-server
pnpm install
pnpm run build

Azure App Registration

1. Go to the Azure Portal
2. Navigate to "App registrations" and create a new registration
3. Name your application (e.g., "To Do MCP")
4. For "Supported account types", select one of the following based on your needs:
   • Accounts in this organizational directory only (Single tenant) - For use within a single organization
   • Accounts in any organizational directory (Any Azure AD directory - Multitenant) - For use across multiple organizations
   • Accounts in any organizational directory and personal Microsoft accounts - For both work accounts and personal accounts
5. Set the Redirect URI to http://localhost:3000/callback
6. After creating the app, go to "Certificates & secrets" and create a new client secret
7. Go to "API permissions" and add the following permissions:
   • Microsoft Graph > Delegated permissions:
     • Tasks.Read
     • Tasks.ReadWrite
     • User.Read
8. Click "Grant admin consent" for these permissions

Configuration

Environment Setup

Create a .env file in the project root (required for authentication):

CLIENT_ID=your_client_id
CLIENT_SECRET=your_client_secret
TENANT_ID=your_tenant_setting
REDIRECT_URI=http://localhost:3000/callback

TENANT_ID Options

• organizations - For multi-tenant organizational accounts (default if not specified)
• consumers - For personal Microsoft accounts only
• common - For both organizational and personal accounts
• your-specific-tenant-id - For single-tenant configurations

Examples:

# For multi-tenant organizational accounts (default)
TENANT_ID=organizations

# For personal Microsoft accounts
TENANT_ID=consumers

# For both organizational and personal accounts
TENANT_ID=common

# For a specific organization tenant
TENANT_ID=00000000-0000-0000-0000-000000000000

Token Storage

The server stores authentication tokens in tokens.json wit

... View full README on GitHub