Microsoft To Do MCP
Turn plans into Microsoft To Do tasks through one hosted MCP endpoint.
Pear uses Microsoft OAuth to expose Microsoft To Do task tools from its hosted endpoint. List and inspect tasks first; creating, updating, completing, deleting, and batch-creating tasks require the applicable write permission and active write policy.
Hosted Microsoft To Do
Keep planning and task execution in the same conversation.
Capture, update, and finish real tasks from an AI workflow.
todo://connectedWhat you can do
- List Microsoft To Do lists and tasks, then fetch one exact task when more detail is needed.
- Create a task or update an existing task after the intended change is approved.
- Mark an exact task complete without treating a planning suggestion as a finished action.
- Delete a selected task only through the applicable destructive-write approval path.
- Batch-create multiple Microsoft To Do tasks from one reviewed set of inputs.
- Use Microsoft OAuth and Pear’s hosted endpoint instead of maintaining Microsoft Graph task scripts.
From setup to your first request
Make the connection. Then make it useful.
Follow your client’s setup guide, then try a request with the accounts you have connected.
Try first
Start with a question.
List my incomplete Microsoft To Do tasks and group them by list.
Show me the exact task named Prepare launch notes before changing it.
Prepare these five action items as a batch of Microsoft To Do tasks for approval.
After I approve it, mark the selected launch task complete.
Setup path
Connect once. Keep your apps close.
Create a Pear account, choose Microsoft 365, and complete Microsoft OAuth.
Follow the maintained setup guide for your chosen AI client and its documented authentication path.
Test a read-only task query first, then approve only the task changes you intend to make.
Why it matters
A little less switching.
Move action items from a conversation into the Microsoft To Do lists you already use.
Create a reviewed batch instead of entering a long task list one item at a time.
Keep completion and deletion separate from suggestions that have not been executed.
- Microsoft OAuth sign-in, not your Microsoft password
- Read and write access stays permission-scoped
- Task writes follow Pear permissions and the active policy
A few good questions
Before you connect.
What Microsoft To Do actions does Pear expose?
Pear exposes tools to list task lists and tasks, get one task, create or update a task, mark a task complete, delete a task, and batch-create tasks. The current client still needs the applicable read or write permission.
Can Pear create several Microsoft To Do tasks at once?
Yes. Pear provides a batch-create tool for a reviewed set of tasks. The batch remains a write action and must pass the same applicable permissions and active write policy.
Does this Microsoft To Do connection control alarms or Apple Reminders?
No. This page covers Microsoft To Do task operations and does not claim alarm support. Pear’s email-follow-up reminder tool is Apple/iCloud-only, and Apple Reminders has separate CalDAV compatibility limits.
Microsoft To Do MCP
Ready to connect your apps?
Pear uses Microsoft OAuth to expose Microsoft To Do task tools from its hosted endpoint. List and inspect tasks first; creating, updating, completing, deleting, and batch-creating tasks require the applicable write permission and active write policy.