Skip to content
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.
Start FreeSee setup guides
Microsoft OAuth sign-in, not your Microsoft password
Read and write access stays permission-scoped
Task writes follow Pear permissions and the active policy
Hosted Microsoft To Do
todo://connected

Capture, update, and finish real tasks from an AI workflow.

Ask your assistant

List my incomplete Microsoft To Do tasks and group them by list.

1

List Microsoft To Do lists and tasks, then fetch one exact task when more detail is needed.

2

Create a task or update an existing task after the intended change is approved.

3

Mark an exact task complete without treating a planning suggestion as a finished action.

What Pear unlocks

Keep planning and task execution in the same conversation.

01

List Microsoft To Do lists and tasks, then fetch one exact task when more detail is needed.

02

Create a task or update an existing task after the intended change is approved.

03

Mark an exact task complete without treating a planning suggestion as a finished action.

04

Delete a selected task only through the applicable destructive-write approval path.

05

Batch-create multiple Microsoft To Do tasks from one reviewed set of inputs.

06

Use Microsoft OAuth and Pear’s hosted endpoint instead of maintaining Microsoft Graph task scripts.

Try first

Prompts that prove the connection is working.

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.
Why it matters

Pear turns one-off chats into finished provider workflows.

The connection carries context into action, while you remain in control of what gets changed.
Outcome 01

Move action items from a conversation into the Microsoft To Do lists you already use.

Outcome 02

Create a reviewed batch instead of entering a long task list one item at a time.

Outcome 03

Keep completion and deletion separate from suggestions that have not been executed.

Keep exploring

Choose the next Pear capability or reference you need.

Microsoft 365 MCP serverSee Microsoft To Do alongside Outlook Mail, Calendar, and Contacts.Outlook Mail MCPUse selected Outlook context before preparing a separate task action.Pear MCP tools referenceInspect the canonical task tools, scopes, and MCP annotations.
FAQ

Answers for agents and search results.

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

Give your assistant a real action layer.

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.
Start FreeSee setup guides