Skip to content

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.

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
  • 52actionsin one signed file
  • 27readlook, never change
  • 15writecreate and update
  • 10wait for a yesdestructive, 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_idEntra application (client) id of an app granted the Microsoft Graph application permission Tasks.ReadWrite.All (or…
    • client_secretEntra client secret for that app
    • tenant_idYour 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 callcheck { 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_idclient_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.0graph.microsoft.com/v1.0
Built from
Microsoft To Do's documentation, read 23 October 2026OpenAPI spec (GitHub)learn.microsoft.com
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.

  • 27readlook, never change
  • 15writecreate and update
  • 10destructivewait 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.

ActionWhat it doesEffectSame name in
m365_graph_todo.tasks.listList tasksList the tasks.readwork.task.list122 connectors
m365_graph_todo.tasks.createCreate a taskCreate a task.writework.task.create127 connectors
m365_graph_todo.task_attachments.listList task file attachmentsList the task file attachments.readwork.task_attachment.list11 connectors
m365_graph_todo.tasks.updateUpdate a taskUpdate a task. Only the fields you pass change.writework.task.update118 connectors
m365_graph_todo.tasks.deleteDelete a taskDelete one task. Graph answers 204 with an empty body.destructivework.task.delete107 connectors
m365_graph_todo.lists.listList task listsList the task lists.readwork.task_list.list9 connectors
m365_graph_todo.task_attachments.getGet a task file attachmentGet one task file attachment.readwork.task_attachment.get9 connectors
m365_graph_todo.lists.deltaTrack changes to task listsGet task lists added, changed or removed (delta query).readwork.task_list.list9 connectors
m365_graph_todo.checklist_items.listList checklist itemsList the checklist items.readwork.checklist_item.list3 connectors
m365_graph_todo.checklist_items.createCreate a checklist itemCreate a checklist item.writework.checklist_item.create3 connectors
m365_graph_todo.list_extensions.listList open extension on a task listsList the open extension on a task lists.readthis connector
m365_graph_todo.task_extensions.listList open extension on a tasksList the open extension on a tasks.readthis 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. Readread

    Which Microsoft To Do tasks are overdue, and who owns each one?

    callsm365_graph_todo.tasks.list

  2. Writewrite

    Create a task in Microsoft To Do. Show me exactly what you will send before you save it.

    callsm365_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 taskm365_graph_todo.tasks.delete
  • Delete a task file attachmentm365_graph_todo.task_attachments.delete
  • Delete a task listm365_graph_todo.lists.delete
  • Delete a checklist itemm365_graph_todo.checklist_items.delete
  • Delete an open extension on a task listm365_graph_todo.list_extensions.delete
  • Delete an open extension on a taskm365_graph_todo.task_extensions.delete
  • Delete a linked resourcem365_graph_todo.linked_resources.delete
  • Delete an attachment upload sessionm365_graph_todo.task_attachment_sessions.delete
  • Delete a task file attachment's contentm365_graph_todo.task_attachments.delete_content
  • Delete an attachment upload session's contentm365_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.

dom365_graph_todo.tasks.deleteconfirm_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: "[email protected]" },    { match: "m365_graph_todo.task_attachments.delete", approver: "[email protected]" },    { match: "m365_graph_todo.lists.delete", approver: "[email protected]" }  ]}
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.

  • 1upstream call per actionall 52 Microsoft To Do actions
  • 52actions pageeach page of a long list is one call
  • 27reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Microsoft To Do action.

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

Tasks52
  • m365_graph_todo.checklist_items.countCount checklist itemsread
  • m365_graph_todo.checklist_items.createCreate a checklist itemwrite
  • m365_graph_todo.checklist_items.deleteDelete a checklist itemdestructive
  • m365_graph_todo.checklist_items.getGet a checklist itemread
  • m365_graph_todo.checklist_items.listList checklist itemsread
  • m365_graph_todo.checklist_items.updateUpdate a checklist itemwrite
  • m365_graph_todo.linked_resources.countCount linked resourcesread
  • m365_graph_todo.linked_resources.createCreate a linked resourcewrite
  • m365_graph_todo.linked_resources.deleteDelete a linked resourcedestructive
  • m365_graph_todo.linked_resources.getGet a linked resourceread
  • m365_graph_todo.linked_resources.listList linked resourcesread
  • m365_graph_todo.linked_resources.updateUpdate a linked resourcewrite
  • m365_graph_todo.list_extensions.countCount open extension on a task listsread
  • m365_graph_todo.list_extensions.createCreate an open extension on a task listwrite
  • m365_graph_todo.list_extensions.deleteDelete an open extension on a task listdestructive
  • m365_graph_todo.list_extensions.getGet an open extension on a task listread
  • m365_graph_todo.list_extensions.listList open extension on a task listsread
  • m365_graph_todo.list_extensions.updateUpdate an open extension on a task listwrite
  • m365_graph_todo.lists.countCount task listsread
  • m365_graph_todo.lists.createCreate a task listwrite
  • m365_graph_todo.lists.deleteDelete a task listdestructive
  • m365_graph_todo.lists.deltaTrack changes to task listsread
  • m365_graph_todo.lists.getGet a task listread
  • m365_graph_todo.lists.listList task listsread
  • m365_graph_todo.lists.updateUpdate a task listwrite
  • m365_graph_todo.task_attachment_sessions.countCount attachment upload sessionsread
  • m365_graph_todo.task_attachment_sessions.deleteDelete an attachment upload sessiondestructive
  • m365_graph_todo.task_attachment_sessions.delete_contentDelete an attachment upload session's contentdestructive
  • m365_graph_todo.task_attachment_sessions.getGet an attachment upload sessionread
  • m365_graph_todo.task_attachment_sessions.listList attachment upload sessionsread
  • m365_graph_todo.task_attachment_sessions.updateUpdate an attachment upload sessionwrite
  • m365_graph_todo.task_attachments.countCount task file attachmentsread
  • m365_graph_todo.task_attachments.createCreate a task file attachmentwrite
  • m365_graph_todo.task_attachments.create_upload_sessionCreate an upload session for a large task attachmentwrite
  • m365_graph_todo.task_attachments.deleteDelete a task file attachmentdestructive
  • m365_graph_todo.task_attachments.delete_contentDelete a task file attachment's contentdestructive
  • m365_graph_todo.task_attachments.getGet a task file attachmentread
  • m365_graph_todo.task_attachments.listList task file attachmentsread
  • m365_graph_todo.task_extensions.countCount open extension on a tasksread
  • m365_graph_todo.task_extensions.createCreate an open extension on a taskwrite
  • m365_graph_todo.task_extensions.deleteDelete an open extension on a taskdestructive
  • m365_graph_todo.task_extensions.getGet an open extension on a taskread
  • m365_graph_todo.task_extensions.listList open extension on a tasksread
  • m365_graph_todo.task_extensions.updateUpdate an open extension on a taskwrite
  • m365_graph_todo.tasks.countCount tasksread
  • m365_graph_todo.tasks.createCreate a taskwrite
  • m365_graph_todo.tasks.deleteDelete a taskdestructive
  • m365_graph_todo.tasks.deltaTrack changes to tasksread
  • m365_graph_todo.tasks.getGet a taskread
  • m365_graph_todo.tasks.listList tasksread
  • m365_graph_todo.tasks.updateUpdate a taskwrite
  • m365_graph_todo.todo.getGet a user's To Do rootread

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.

Give your agent Microsoft To Do today.

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