---
title: "Microsoft To Do MCP server for AI agents - actionlake"
description: "Give Claude 52 Microsoft To Do actions through one MCP server: tasks, task attachments. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/microsoft-to-do
updated: 2026-10-23
---

Connectors · Work & projects

# Microsoft To Do MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Microsoft To Do and the rest of your systems. It gives your agent 52 Microsoft To Do actions (27 reads, 15 writes and 10 that wait for a confirmation) and holds the Microsoft To Do credential itself, so the agent never does. It paces Microsoft To Do's limits and records every call.

[Connect Microsoft To Do free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "m365_graph_todo.todo.get",
  intent: "check which Microsoft To Do account is connected"
}
# Get a user's To Do root · read · 1 upstream call
```

- 52 actions in one signed file
- 27 read look, never change
- 15 write create and update
- 10 wait for a yes destructive, confirmed first

Set up

## Connect Microsoft To Do in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Microsoft To Do.
   OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `client_id` Entra application (client) id of an app granted the Microsoft Graph application permission Tasks.ReadWrite.All (or…
   - `client_secret` Entra client secret for that app
   - `tenant_id` Your Microsoft To Do tenant id
   ```
   account { op: "connections.requirements", service: "m365_graph_todo" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "m365_graph_todo.todo.get" }
   # get a user's to do root · read · 1 upstream call
   check { action: "m365_graph_todo.tasks.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Microsoft To Do at a glance

**Sign-in**

OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in.

**You provide**

`client_id` `client_secret`

**Setup fields**

`tenant_id`

**Limits we pace to**

10,000 calls per 10 minutes, per connection

**API covered**

Microsoft To Do (Microsoft Graph) API v1.0`graph.microsoft.com/v1.0`

**Built from**

Microsoft To Do's documentation, read 23 October 2026[OpenAPI spec (GitHub)](https://raw.githubusercontent.com/microsoftgraph/msgraph-metadata/master/openapi/v1.0/openapi.yaml) [learn.microsoft.com](https://learn.microsoft.com/en-us/graph/api/resources/todo-overview)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

27 of 27 reads, for up to an hour; a write clears what it affects

**Shared entities**

3, so ask can line Microsoft To Do up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Microsoft To Do.

52 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.

- **27** read look, never change
- **15** write create and update
- **10** destructive wait for a confirmation

1. ### Tasks
   52
   27 read · 15 write · 10 destructive
   List tasks · Create a task · Track changes to tasks · List task file attachments

Top actions

## The Microsoft To Do API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 20 of Microsoft To Do's 23 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `m365_graph_todo.tasks.list` List tasks | List the tasks. | read | `work.task.list` 122 connectors |
| `m365_graph_todo.tasks.create` Create a task | Create a task. | write | `work.task.create` 127 connectors |
| `m365_graph_todo.task_attachments.list` List task file attachments | List the task file attachments. | read | `work.task_attachment.list` 11 connectors |
| `m365_graph_todo.tasks.update` Update a task | Update a task. Only the fields you pass change. | write | `work.task.update` 118 connectors |
| `m365_graph_todo.tasks.delete` Delete a task | Delete one task. Graph answers 204 with an empty body. | destructive | `work.task.delete` 107 connectors |
| `m365_graph_todo.lists.list` List task lists | List the task lists. | read | `work.task_list.list` 9 connectors |
| `m365_graph_todo.task_attachments.get` Get a task file attachment | Get one task file attachment. | read | `work.task_attachment.get` 9 connectors |
| `m365_graph_todo.lists.delta` Track changes to task lists | Get task lists added, changed or removed (delta query). | read | `work.task_list.list` 9 connectors |
| `m365_graph_todo.checklist_items.list` List checklist items | List the checklist items. | read | `work.checklist_item.list` 3 connectors |
| `m365_graph_todo.checklist_items.create` Create a checklist item | Create a checklist item. | write | `work.checklist_item.create` 3 connectors |
| `m365_graph_todo.list_extensions.list` List open extension on a task lists | List the open extension on a task lists. | read | this connector |
| `m365_graph_todo.task_extensions.list` List open extension on a tasks | List the open extension on a tasks. | read | this connector |

Try it

## Prompts to paste into Claude.

Each one names the Microsoft To Do actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Which Microsoft To Do tasks are overdue, and who owns each one?
   calls `m365_graph_todo.tasks.list`
2. Write write
   Create a task in Microsoft To Do. Show me exactly what you will send before you save it.
   calls `m365_graph_todo.tasks.create`

Governance for Microsoft To Do

## Destructive actions wait for a yes.

10 Microsoft To Do actions are destructive. These are all of them:

- Delete a task `m365_graph_todo.tasks.delete`
- Delete a task file attachment `m365_graph_todo.task_attachments.delete`
- Delete a task list `m365_graph_todo.lists.delete`
- Delete a checklist item `m365_graph_todo.checklist_items.delete`
- Delete an open extension on a task list `m365_graph_todo.list_extensions.delete`
- Delete an open extension on a task `m365_graph_todo.task_extensions.delete`
- Delete a linked resource `m365_graph_todo.linked_resources.delete`
- Delete an attachment upload session `m365_graph_todo.task_attachment_sessions.delete`
- Delete a task file attachment's content `m365_graph_todo.task_attachments.delete_content`
- Delete an attachment upload session's content `m365_graph_todo.task_attachment_sessions.delete_content`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do m365_graph_todo.tasks.delete confirm_policy: **human**

Delete a task?

**intent:** the user asked me to delete a task

run suspended · waiting for a named person · key _m365-graph-todo-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "m365-graph-todo-agent",
  allowed_actions: ["m365_graph_todo.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "m365_graph_todo.tasks.delete", approver: "lead@example.com" },
    { match: "m365_graph_todo.task_attachments.delete", approver: "lead@example.com" },
    { match: "m365_graph_todo.lists.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Microsoft To Do only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Microsoft To Do costs on actionlake.

Every Microsoft To Do action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Microsoft To Do refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 52 Microsoft To Do actions
- 52 actions page each page of a long list is one call
- 27 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Microsoft To Do action.

52 actions by area: the id your agent calls, what it does, and its effect.

**Tasks 52**

- `m365_graph_todo.checklist_items.count` Count checklist items read
- `m365_graph_todo.checklist_items.create` Create a checklist item write
- `m365_graph_todo.checklist_items.delete` Delete a checklist item destructive
- `m365_graph_todo.checklist_items.get` Get a checklist item read
- `m365_graph_todo.checklist_items.list` List checklist items read
- `m365_graph_todo.checklist_items.update` Update a checklist item write
- `m365_graph_todo.linked_resources.count` Count linked resources read
- `m365_graph_todo.linked_resources.create` Create a linked resource write
- `m365_graph_todo.linked_resources.delete` Delete a linked resource destructive
- `m365_graph_todo.linked_resources.get` Get a linked resource read
- `m365_graph_todo.linked_resources.list` List linked resources read
- `m365_graph_todo.linked_resources.update` Update a linked resource write
- `m365_graph_todo.list_extensions.count` Count open extension on a task lists read
- `m365_graph_todo.list_extensions.create` Create an open extension on a task list write
- `m365_graph_todo.list_extensions.delete` Delete an open extension on a task list destructive
- `m365_graph_todo.list_extensions.get` Get an open extension on a task list read
- `m365_graph_todo.list_extensions.list` List open extension on a task lists read
- `m365_graph_todo.list_extensions.update` Update an open extension on a task list write
- `m365_graph_todo.lists.count` Count task lists read
- `m365_graph_todo.lists.create` Create a task list write
- `m365_graph_todo.lists.delete` Delete a task list destructive
- `m365_graph_todo.lists.delta` Track changes to task lists read
- `m365_graph_todo.lists.get` Get a task list read
- `m365_graph_todo.lists.list` List task lists read
- `m365_graph_todo.lists.update` Update a task list write
- `m365_graph_todo.task_attachment_sessions.count` Count attachment upload sessions read
- `m365_graph_todo.task_attachment_sessions.delete` Delete an attachment upload session destructive
- `m365_graph_todo.task_attachment_sessions.delete_content` Delete an attachment upload session's content destructive
- `m365_graph_todo.task_attachment_sessions.get` Get an attachment upload session read
- `m365_graph_todo.task_attachment_sessions.list` List attachment upload sessions read
- `m365_graph_todo.task_attachment_sessions.update` Update an attachment upload session write
- `m365_graph_todo.task_attachments.count` Count task file attachments read
- `m365_graph_todo.task_attachments.create` Create a task file attachment write
- `m365_graph_todo.task_attachments.create_upload_session` Create an upload session for a large task attachment write
- `m365_graph_todo.task_attachments.delete` Delete a task file attachment destructive
- `m365_graph_todo.task_attachments.delete_content` Delete a task file attachment's content destructive
- `m365_graph_todo.task_attachments.get` Get a task file attachment read
- `m365_graph_todo.task_attachments.list` List task file attachments read
- `m365_graph_todo.task_extensions.count` Count open extension on a tasks read
- `m365_graph_todo.task_extensions.create` Create an open extension on a task write
- `m365_graph_todo.task_extensions.delete` Delete an open extension on a task destructive
- `m365_graph_todo.task_extensions.get` Get an open extension on a task read
- `m365_graph_todo.task_extensions.list` List open extension on a tasks read
- `m365_graph_todo.task_extensions.update` Update an open extension on a task write
- `m365_graph_todo.tasks.count` Count tasks read
- `m365_graph_todo.tasks.create` Create a task write
- `m365_graph_todo.tasks.delete` Delete a task destructive
- `m365_graph_todo.tasks.delta` Track changes to tasks read
- `m365_graph_todo.tasks.get` Get a task read
- `m365_graph_todo.tasks.list` List tasks read
- `m365_graph_todo.tasks.update` Update a task write
- `m365_graph_todo.todo.get` Get a user's To Do root read

Questions

## The Microsoft To Do MCP server, answered.

**Is there a Microsoft To Do MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 52 Microsoft To Do actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Microsoft To Do.

**What do I need to connect Microsoft To Do?**

Entra application (client) id of an app granted the Microsoft Graph application permission Tasks.ReadWrite.All (or… and Entra client secret for that app. Plus your tenant id. The free call account { op: "connections.requirements", service: "m365_graph_todo" } lists exactly what to paste.

**Can an AI agent delete or change things in Microsoft To Do?**

Only if its key allows it, and only with an explicit confirmation. 10 Microsoft To Do actions are destructive, including delete a task, delete a task file attachment and delete a task list. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Microsoft To Do API limit?**

actionlake paces every call to the limits in the Microsoft To Do service file: 10,000 calls per 10 minutes per connection. Repeated reads are answered from cache (27 Microsoft To Do actions can be), which never reaches Microsoft To Do.

**What does a Microsoft To Do action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (52 Microsoft To Do actions page). Cache hits, searches, dry runs and calls Microsoft To Do refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Microsoft To Do API does it cover?**

The Microsoft To Do (Microsoft Graph) API v1.0 at graph.microsoft.com/v1.0. It is built from Microsoft To Do's documentation as read on 23 October 2026. 52 actions in 1 area, each one in the signed service file (version 1.0.0).

**Does actionlake keep my Microsoft To Do data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Microsoft To Do credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Microsoft To Do

Shares the most action names with

- [Trello 18](https://actionlake.com/connectors/trello)
- [Zoho Projects 11](https://actionlake.com/connectors/zoho-projects)
- [Process Street 8](https://actionlake.com/connectors/process-street)
- [ClickUp 7](https://actionlake.com/connectors/clickup)
- [Microsoft Planner 5](https://actionlake.com/connectors/microsoft-planner)
- [Fieldwire 5](https://actionlake.com/connectors/fieldwire)

Joins with, on shared entities

- [HubSpot CRM 1](https://actionlake.com/connectors/hubspot-crm)
- [ServiceNow 1](https://actionlake.com/connectors/servicenow)
- [Bitrix24 1](https://actionlake.com/connectors/bitrix24)
- [Simpro 1](https://actionlake.com/connectors/simpro)
- [Acumatica Cloud ERP 1](https://actionlake.com/connectors/acumatica-cloud-erp)
- [GitLab 1](https://actionlake.com/connectors/gitlab)

Browse

- [All Work & projects connectors](https://actionlake.com/connectors/category/work-and-projects)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Microsoft To Do; the name is the vendor's own. Counts are from the Microsoft To Do service file, version 1.0.0.

## Give your agent Microsoft To Do today.

[Connect Microsoft To Do free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/microsoft-to-do
More: https://actionlake.com/llms.txt
