How to connect Microsoft To Do to OpenClaw
Connect Microsoft To Do to OpenClaw with ClawLink in one click — 22 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
Microsoft To DoOAUTH2MCPManage task lists, tasks, and checklist items. Once connected, OpenClaw can read and act on Microsoft To Do from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Microsoft To Do access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Microsoft To Do setup: install one ClawHub skill, connect Microsoft To Do in the browser, and OpenClaw can call real Microsoft To Do actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Microsoft To Do.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Microsoft To Do
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Microsoft To Do?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Microsoft To Do in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
List my Microsoft To Do task lists and the open tasks in each one.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Microsoft To Do is connected in the dashboard, that agent calls the same 22 Microsoft To Do tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Microsoft To Do MCP for OpenClaw
Looking for a Microsoft To Do MCP server for OpenClaw? ClawLink connects Microsoft To Do to OpenClaw and exposes 22 Microsoft To Do tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Microsoft To Do integration works the same way.
What the OpenClaw Microsoft To Do integration can do
22 Microsoft To Do tools are ready for OpenClaw once the account is connected. The 18 below are the ones people reach for most; your agent can call all 22.
18 of 22 Microsoft To Do tools for OpenClaw
| Tool | What it does |
|---|---|
Download task attachment microsoft_todo_download_task_attachment | Download one file attached to a Microsoft To Do task |
Get checklist item microsoft_todo_get_checklist_item | Get a single Microsoft To Do checklist item (subtask) by its id, within a task in a task list |
Get current user microsoft_todo_get_current_user | Return the profile of the Microsoft account connected to this toolkit (whoami / connection |
Get task microsoft_todo_get_task | Get a single Microsoft To Do task by its id, within a task list |
Get task attachment microsoft_todo_get_task_attachment | Get metadata for one file attached to a Microsoft To Do task |
Get task list microsoft_todo_get_task_list | Get a single Microsoft To Do task list by its id |
List checklist items microsoft_todo_list_checklist_items | List the checklist items (subtasks) of a To Do task |
List task attachments microsoft_todo_list_task_attachments | List the files attached to a Microsoft To Do task |
List task lists microsoft_todo_list_task_lists | List the To Do task lists owned by the connected user |
List tasks microsoft_todo_list_tasks | List the tasks in a To Do task list |
Complete task microsoft_todo_complete_task | Mark a Microsoft To Do task as completed |
Create checklist item microsoft_todo_create_checklist_item | Add a checklist item (subtask) to a Microsoft To Do task |
Create task microsoft_todo_create_task | Create a task in a Microsoft To Do task list |
Create task list microsoft_todo_create_task_list | Create a new Microsoft To Do task list |
Update checklist item microsoft_todo_update_checklist_item | Update a checklist item (subtask) of a Microsoft To Do task: rename it (display_name) and/or |
Update task microsoft_todo_update_task | Update fields of an existing Microsoft To Do task (title, notes, importance, status |
Update task list microsoft_todo_update_task_list | Rename a Microsoft To Do task list (updates its displayName) |
Upload task attachment microsoft_todo_upload_task_attachment | Attach a file up to 25 MB to a Microsoft To Do task |
Try it: find the Microsoft To Do tool you need
Browse the 18 Microsoft To Do tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
List my Microsoft To Do task lists and the open tasks in each one.
Add a task "Renew passport" to my Personal list, due next Friday.
Add checklist items to my "Plan trip" task: book flights, book hotel, pack.
Mark "Send invoice" as complete in Microsoft To Do.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Microsoft To Do working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Microsoft To Do app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Microsoft To Do through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Microsoft To Do. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Microsoft To Do actions to the runtime in a format your agent can reliably use. | 22 tools for Microsoft To Do are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Microsoft To Do to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Microsoft To Do in the browser, and the 22 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Microsoft To Do skill but can't call the tools
The ClawHub skill teaches OpenClaw about Microsoft To Do, but the calls run through the ClawLink plugin and your connected account. Make sure Microsoft To Do is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Microsoft To Do from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Microsoft To Do tools
Microsoft To Do tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Microsoft To Do call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Microsoft To Do returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
Need admin approval
Your work or school Microsoft account blocks you from approving new apps yourself. ClawLink's Microsoft app is not publisher-verified yet, and many organizations only let an IT admin approve apps like that. Ask your IT admin to approve ClawLink once for the organization. Personal Microsoft accounts (Outlook.com, Hotmail, Live) do not see this screen.
OAuth finished in the browser but the account is still missing
Try reconnecting Microsoft To Do and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Microsoft To Do integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Microsoft To Do: link your Microsoft To Do account once in the browser and OpenClaw can call the Microsoft To Do API through 22 ready-made tools — no custom code or token handling.
How do I add Microsoft To Do to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Microsoft To Do skill from ClawHub, then you click Connect in the dashboard to authorize Microsoft To Do. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Microsoft To Do to OpenClaw?
About two minutes. Sign in, click Connect next to Microsoft To Do in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Microsoft To Do up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Microsoft To Do working from chat.
OpenClaw installed the Microsoft To Do skill but can't call the tools
The ClawHub skill teaches OpenClaw about Microsoft To Do, but the calls run through the ClawLink plugin and your connected account. Make sure Microsoft To Do is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
