mcpField
M
microsoft-todo-mcp-server

microsoft-todo-mcp-server

Local
github.com/jordanburkeOther118Updated 1d ago

About microsoft-todo-mcp-server

microsoft-todo-mcp-server lets AI assistants manage Microsoft To Do through Microsoft Graph. It is for Microsoft account users who want task operations via an assistant, with support for lists, tasks, checklist items, and OAuth token refresh.

Key features

  1. 01Create, update, and delete task lists
  2. 02Manage tasks and their properties
  3. 03Manage task checklist items
  4. 04OAuth authentication and automatic token refresh
  5. 05Support personal, work, and school accounts

Use cases

  1. 01View and filter tasks through an AI assistant
  2. 02Create tasks with due dates or reminders
  3. 03Maintain subtasks within a task

MCP support

The MCP server exposes Microsoft To Do management tools to clients such as Claude and Cursor, using Microsoft Graph to access account data. It authenticates with OAuth 2.0 and refreshes tokens automatically.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"jordanburke-microsoft-todo": {
"command": "npx",
"args": [
"-y",
"microsoft-todo-mcp-server"
],
"env": {
"MS_TODO_ACCESS_TOKEN": "<MS_TODO_ACCESS_TOKEN>",
"MS_TODO_REFRESH_TOKEN": "<MS_TODO_REFRESH_TOKEN>",
"CLIENT_ID": "<CLIENT_ID>",
"CLIENT_SECRET": "<CLIENT_SECRET>",
"TENANT_ID": "<TENANT_ID>"
}
}
}
}
Run commandnpx -y microsoft-todo-mcp-server
Environment variables to set
MS_TODO_ACCESS_TOKENSecretMicrosoft Graph access token. Must be set together with MS_TODO_REFRESH_TOKEN; `mstodo-config` emits both.
MS_TODO_REFRESH_TOKENSecretRefresh token. Required alongside the access token, but note the env-token path does not renew: once the access token expires the server returns 401 until it is replaced.
CLIENT_IDAzure AD application (client) ID. The server reads it to refresh tokens when the stored token file carries no credentials; `mstodo-setup` also uses it.
CLIENT_SECRETSecretAzure AD client secret, used for the same token refresh and by `mstodo-setup`.
TENANT_IDAzure AD tenant: 'organizations' (the default), 'consumers', 'common', or a tenant GUID.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmmicrosoft-todo-mcp-server1.1.4

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Microsoft To Do MCP

CI npm version

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. It looks in three places, in order:

  1. MSTODO_TOKEN_FILE, if set
  2. the per-user config directory — ~/.config/microsoft-todo-mcp/tokens.json, or %APPDATA%\microsoft-todo-mcp\tokens.json on Windows
  3. tokens.json in the working directory, which is migrated to whichever of (1) or (2) is in effect on first read
# Override the location
export MSTODO_TOKEN_FILE=/path/to/custom/tokens.json

You can also supply tokens directly, which takes precedence over the file:

export MS_TODO_ACCESS_TOKEN=your_access_token
export MS_TODO_REFRESH_TOKEN=your_refresh_token

These two are a starting point, not a live store — nothing rewrites your environment when a token is renewed. A renewal is kept for the rest of the session and written to the token file, and the environment pair is not consulted again.

How the expiry is known depends on your account type. Work and school accounts get a JWT access token, so the server reads the real deadline from it and renews 5 minutes early. Personal accounts get an opaque token, where there is nothing to read and the server assumes an hour from when it first saw the value. Either way renewal needs CLIENT_ID and CLIENT_SECRET; without them the server cannot refresh, and calls start failing once the supplied token runs out.

Usage

Complete Setup Workflow
Step 1: Authenticate with Microsoft
# If installed globally
git clone https://github.com/jordanburke/microsoft-todo-mcp-server.git
cd microsoft-todo-mcp-server
pnpm install
pnpm run auth

# Or if running locally
pnpm run auth

This opens a browser window for Microsoft authentication and creates a tokens.json file.

Step 2: Create MCP Configuration
# Generate MCP configuration file
pnpm run create-config

# Or use the global helper (if installed globally)
mstodo-config

This creates an mcp.json file with your authentication tokens.

Step 3: Configure Your AI Assistant

For Claude Desktop:

Add to your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "microsoftTodo": {
      "command": "npx",
      "args": ["--yes", "microsoft-todo-mcp-server"],
      "env": {
        "MS_TODO_ACCESS_TOKEN": "your_access_token",
        "MS_TODO_REFRESH_TOKEN": "your_refresh_token"
      }
    }
  }
}

For Cursor:

# Copy to Cursor's global configuration
cp mcp.json ~/.cursor/mcp-servers.json
Available Scripts
# Development & Building
pnpm run build        # Build TypeScript to JavaScript
pnpm run dev          # Build and run CLI in one command

# Running the Server
pnpm start            # Run MCP server directly
pnpm run cli          # Run MCP server via CLI wrapper
npx microsoft-todo-mcp-server  # Run globally installed version

# Authentication & Configuration
pnpm run auth         # Start OAuth authentication server
pnpm run create-config # Generate mcp.json from tokens.json

# Code Quality
pnpm run format       # Format code with Prettier
pnpm run format:check # Check code formatting
pnpm run lint         # Run linting checks
pnpm run typecheck    # TypeScript type checking

MCP Tools

The server provides 13 tools for comprehensive Microsoft To Do management:

Authentication
  • auth-status - Check authentication status, token expiration, and account type
Task Lists (Top-level Containers)
  • get-task-lists - Retrieve all task lists with metadata (default, shared, etc.)
  • create-task-list - Create a new task list
  • update-task-list - Rename an existing task list
  • delete-task-list - Delete a task list and all its contents
Tasks (Main Todo Items)
  • get-tasks - Get tasks from a list with filtering, sorting, and pagination
    • Supports OData query parameters: $filter, $select, $orderby, $top, $skip, $count
  • create-task - Create a new task with full property support
    • Title, description, due date, start date, importance, reminders, status, categories
  • update-task - Update any task properties
  • delete-task - Delete a task and all its checklist items
Checklist Items (Subtasks)
  • get-checklist-items - Get subtasks for a specific task
  • create-checklist-item - Add a new subtask to a task
  • update-checklist-item - Update subtask text or completion status
  • delete-checklist-item - Remove a specific subtask

Architecture

Project Structure
  • MCP Server (src/todo-index.ts) - Core server implementing the MCP protocol
  • CLI Wrapper (src/cli.ts) - Executable entry point with token management
  • Auth Server (src/auth-server.ts) - Express server for OAuth 2.0 flow
  • Config Generator (src/create-mcp-config.ts) - Helper to create MCP configurations
Technical Details
  • Microsoft Graph API: Uses v1.0 endpoints
  • Authentication: MSAL (Microsoft Authentication Library) with PKCE flow
  • Token Management: Automatic refresh 5 minutes before expiration
  • Build System: ts-builds (tsdown) for fast TypeScript compilation
  • Module System: ESM (ECMAScript modules)

Limitations & Known Issues

Personal Microsoft Accounts
  • MailboxNotEnabledForRESTAPI Error: Personal Microsoft accounts (outlook.com, hotmail.com, live.com) have limited access to the To Do API through Microsoft Graph
  • This is a Microsoft service limitation, not an issue with this application
  • Work/school accounts have full API access
API Limitations
  • Rate limits apply according to Microsoft's policies
  • Some features may be unavailable for personal accounts
  • Shared lists have limited functionality

Troubleshooting

Authentication Issues

Token acquisition failures

  • Verify CLIENT_ID, CLIENT_SECRET, and TENANT_ID in your .env file
  • Ensure redirect URI matches exactly: http://localhost:3000/callback
  • Check Azure App permissions are granted with admin consent

Permission issues

  • Ensure all required Graph API permissions are added and consented
  • For organizational accounts, admin consent may be required
Account Type Configuration

Work/School Accounts

TENANT_ID=organizations  # Multi-tenant
# Or use your specific tenant ID

Personal Accounts

TENANT_ID=consumers  # Personal only
# Or TENANT_ID=common for both types
Debugging

Check authentication status:

# Using the MCP tool
# In your AI assistant: "Check auth status"

# Or examine tokens directly
cat tokens.json | jq '.expiresAt'

# Convert timestamp to readable date
date -d @$(($(cat tokens.json | jq -r '.expiresAt') / 1000))

Enable verbose logging:

# The server logs to stderr for debugging
mstodo 2> debug.log

Contributing

Contributions are welcome! Please:

  1. Fork the repository
  2. Create a feature branch
  3. Run pnpm run lint and pnpm run typecheck before submitting
  4. Submit a pull request

License

MIT License - See LICENSE file for details

Acknowledgments

Support

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.