Todomcp

🚀 Microsoft To Do MCP Service Description

This MCP (Model Context Protocol) service allows you to interact with Microsoft To Do tasks through an AI assistant.

🚀 Quick Start

This MCP service enables seamless interaction with Microsoft To Do tasks via an AI assistant.

✨ Features

• Interact with Microsoft To Do tasks through an AI assistant.
• A comprehensive set of commands for task and category management.

📦 Installation

1. Prerequisites

• Node.js version 16 or higher
• npm
• A Microsoft account
• Azure application registration (see setup instructions below)

2. Installation Steps

Installing this tool involves two main parts:

1. Installing the package
2. Setting up authentication (requires cloning the repository)

Step 1: Install the Package

npm install -g @jhirono/todomcp

Step 2: Set Up Authentication

Even if you've installed the package globally, you still need to clone the repository to complete the authentication process:

git clone https://github.com/jhirono/todoMCP.git
cd todoMCP
npm install

3. Azure Application Registration

1. Visit 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", choose one of the following options based on your needs:
   • Accounts in this organizational directory only (Single tenant) - For use within a single organization.
   • Accounts in any organizational directory (Multi tenant) - For use across multiple organizations.
   • Work or school accounts - Specifically for educational or corporate environments.
5. In the "Application authentication" section, configure sessions and API permissions.
6. Create a client secret to obtain the CLIENT_SECRET value.

4. Configuration Guide

Create a .env file in the project root directory and add the following content:

CLIENT_ID=your_client_id_here
CLIENT_SECRET=your_client_secret_here
TENANT_ID=your_tenant_id_here

Replace your_client_id_here, your_client_secret_here, and your_tenant_id_here with the actual values from your Azure registration.

5. Usage Instructions

After installation, you can use the MCP tool with the following command:

mcp --help

This will display all available commands and their detailed options. For the usage of specific commands, refer to the documentation.

💻 Usage Examples

Basic Usage

To list all tasks, use the following command:

mcp list-tasks

Advanced Usage

To create a new task with specific details, you can use the create-task command with additional parameters. For example:

mcp create-task --title "New Task" --due-date "2024-12-31"

📚 Documentation

Available Tools

Here is a complete list of commands you can use:

• list-tasks: Get all tasks.
• get-task: Get detailed information about a single task.
• create-task: Create a new task.
• update-task: Update an existing task.
• delete-task: Delete a specified task.
• list-categories: Get all categories.
• get-category: Get detailed information about a single category.
• create-category: Create a new category.
• update-category: Update an existing category.
• delete-category: Delete a specified category.

Limitations and Notes

• The API requires proper authentication and permissions.
• Microsoft policies may impose rate limits.

Troubleshooting

Authentication Issues

• "MailboxNotEnabledForRESTAPI" error: This usually indicates that you're using a personal Microsoft account. Accessing the To Do API via the Graph API has limitations for personal accounts.

• Token acquisition failure: Ensure that the CLIENT_ID, CLIENT_SECRET, and TENANT_ID in the .env file are correct.

• Permission issues: Confirm that the required administrative consent permissions have been granted in the Azure application registration.

Account Type Issues

• Work/school accounts: These are generally the best fit for using the To Do API. Use TENANT_ID=organizations or your specific tenant ID.

• Personal accounts: These have limited access to the To Do API. If you must use a personal account, try TENANT_ID=consumers or TENANT_ID=common.

Checking Authentication Status

You can check the authentication status using the auth-status tool or by viewing the token's expiration time:

cat tokens.json | grep expiresAt

To convert the timestamp to a readable date:

date -r $(echo "$(cat tokens.json | grep expiresAt | cut -d ":" -f2 | cut -d "," -f1) / 1000" | bc)