Files and knowledge
Microsoft To Do for AI agents.
Managed auth, ready-made tools.
Create, update and complete tasks across task lists in Microsoft To Do on behalf of each of your users.
About Microsoft To Do
With the Microsoft To Do connector, your agent manages tasks in each user’s own Microsoft To Do. It can list their task lists and tasks, add a task with a due date, update or complete it, and create a new list, using only the tools your project allows.
Microsoft To Do is Microsoft’s task app for personal and work to-do lists.
Tools
What your agent can do in Microsoft To Do.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Microsoft To Do connection.
-
List task lists
Readmicrosoft_todo_list_task_listsList the user's task lists.
-
List tasks
Readmicrosoft_todo_list_tasksGet the tasks in a list, open or completed.
-
Create a task
Writemicrosoft_todo_create_taskAdd a task with a title, notes, due date and reminder.
-
Update a task
Writemicrosoft_todo_update_taskChange a task's details or mark it as completed.
-
Delete a task
Writemicrosoft_todo_delete_taskRemove a task.
-
Create a task list
Writemicrosoft_todo_create_task_listCreate a new task list.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Microsoft To Do, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read and add tasks, and switch off
microsoft_todo_delete_taskso it can never remove one. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example reading tasks but not changing them. A call outside them is refused.
Get started
Connect Microsoft To Do
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Microsoft To Do
Each end user authorizes their own Microsoft To Do account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Microsoft To Do account, once. const connection = await agent200 .user("user_123") .connect("microsoft_to_do"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Microsoft To Do tools
Name the user, the model and the tools. The model decides which Microsoft To Do tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Add call the landlord to my To Do list for tomorrow", tools: ["microsoft_to_do"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Microsoft's own sign-in page. You never see or store their Microsoft To Do password.
-
What access is requested
The scopes the connection needs, such as reading tasks or reading and writing tasks, listed on Microsoft's consent screen. Users can remove the app later from their Microsoft account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Microsoft To Do connector and how to use it.
Connector: Microsoft To Do, through Agent200. In code: "microsoft_to_do". What it does: Create, update and complete tasks across task lists in Microsoft To Do on behalf of each of your users. Page: https://www.agent200.com/connectors/microsoft-to-do/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Microsoft To Do's own page, through the authorization link Agent200 returns. Never ask a user for a Microsoft To Do password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: microsoft_todo_list_task_lists, microsoft_todo_list_tasks. Write tools: microsoft_todo_create_task, microsoft_todo_update_task, microsoft_todo_delete_task, microsoft_todo_create_task_list. Name "microsoft_to_do" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/microsoft-to-do/framework/claude/ https://www.agent200.com/connectors/microsoft-to-do/framework/chatgpt/ https://www.agent200.com/connectors/microsoft-to-do/framework/claude-code/ https://www.agent200.com/connectors/microsoft-to-do/framework/muse/ https://www.agent200.com/connectors/microsoft-to-do/framework/grok-bot/ https://www.agent200.com/connectors/microsoft-to-do/framework/openai-dots/ https://www.agent200.com/connectors/microsoft-to-do/framework/claude-duet/ https://www.agent200.com/connectors/microsoft-to-do/framework/hermes-agent/ https://www.agent200.com/connectors/microsoft-to-do/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/microsoft-to-do.md
Guides
Use Microsoft To Do with the AI you build on.
Step-by-step setup for Microsoft To Do with a specific model, assistant or agent framework.
-
Microsoft To Do + Claude
How to connect Microsoft To Do to Claude
-
Microsoft To Do + ChatGPT
How to connect Microsoft To Do to ChatGPT
-
Microsoft To Do + Claude Code
How to connect Microsoft To Do to Claude Code
-
Microsoft To Do + Muse
How to connect Microsoft To Do to Muse
-
Microsoft To Do + Grok Bot
How to connect Microsoft To Do to Grok Bot
-
Microsoft To Do + OpenAI Dots
How to connect Microsoft To Do to OpenAI Dots
-
Microsoft To Do + Claude Duet
How to connect Microsoft To Do to Claude Duet
-
Microsoft To Do + Hermes Agent
How to connect Microsoft To Do to Hermes Agent
-
Microsoft To Do + OpenClaw
How to connect Microsoft To Do to OpenClaw
FAQ
Microsoft To Do and Agent200, answered.
Who handles the Microsoft To Do OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Microsoft To Do.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Microsoft To Do connection, never another user's. It cannot reach anything the user or Microsoft To Do has not authorized.
Can I limit what my agent can do in Microsoft To Do?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.