Productivity & Project Management · Microsoft To Do + Claude
Microsoft To Do MCP with Claude: Turn Conversations into Organised Tasks
The short answer
Claude works with Microsoft To Do through the Model Context Protocol, an open standard that lets Claude securely read and act within the app using permissions you control. Once connected, Claude can create tasks, manage task lists, update checklist items and set reminders from natural language instructions, with people approving consequential changes.
What is Microsoft To Do?
Microsoft To Do is Microsoft's cloud task management app. It holds lists, tasks, checklist items, reminders and due dates, and keeps personal and team work in step across phones, tablets and computers. It is used by individuals organising their day, and by teams tracking shared follow-ups. Because it runs on Microsoft Graph, it sits naturally alongside other Microsoft 365 tools that many organisations already use.
How Claude connects to Microsoft To Do through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other software. It lets Claude use a tool securely, reading information and taking actions, with access that the organisation sets and controls.
Once Microsoft To Do is connected, Claude can typically create a new task from a request, add checklist items to an existing task, move work between lists, and set reminders or due dates. A manager could ask in plain English for a follow-up to be added to the team list for Friday, and Claude would carry it out in the app.
Permissions and approvals keep people in charge. Access is limited to the lists and actions the organisation allows, and sign-in uses OAuth, the standard method Microsoft To Do supports. Consequential changes can be routed for human approval before they are made, and activity can be logged for review.
What you can automate
Capturing action items from meetings
After a team meeting, a project lead pastes the notes into Claude and asks for each action to be turned into a task with an owner and due date. Claude creates the tasks in the right list, adds checklist items for sub-steps and sets reminders. The team starts the next day with a clear, shared list rather than scattered notes.
Personal daily planning
An executive asks Claude each morning to review open tasks and add reminders for the three most time-sensitive items. Claude reads the lists, flags overdue work and sets reminders in the app. This helps busy leaders keep commitments visible without spending time on admin.
Customer follow-up tracking
A sales or account team member describes new follow-ups in plain language after a call. Claude creates a task for each one, sets a due date and places it in the correct client list. Nothing is missed between calls and the pipeline stays organised.
Onboarding checklists for new staff
HR or an operations manager asks Claude to create a standard onboarding task list for each new starter, with checklist items for equipment, accounts and training. Claude sets reminders for the first week. New joiners get a consistent experience every time.
Event and campaign preparation
A marketing lead asks Claude to build a launch checklist for an upcoming campaign, with tasks grouped by owner and deadline. Claude updates the list as items are completed and sets reminders ahead of key dates. The whole team sees progress in one place.
An end-to-end workflow: Meeting actions to tracked tasks
TriggerA project meeting ends and the lead shares the notes with Claude.
Claude reads the notes and identifies each action, owner and deadline.
Claude checks the relevant team list in Microsoft To Do to avoid duplicates.
Claude creates a task for each action with the due date and assigned details recorded in the task.
Claude adds checklist items for any sub-steps mentioned in the notes.
Claude sets reminders ahead of each deadline and posts a summary for the lead to review.
The lead approves the summary, and the tasks remain visible to the team in Microsoft To Do.
OutcomeActions from meetings are captured within minutes, with clear deadlines and reminders, and fewer follow-ups are lost between meetings. Typical results vary by team and process.
How we set it up
Free automation audit
We review how your teams use Microsoft To Do today and identify the routines worth automating, such as meeting follow-ups, onboarding lists and personal planning.
Secure connection
We connect Claude to Microsoft To Do using OAuth sign-in, the method the app supports, with least-privilege access limited to the lists and actions you approve.
Workflow design
We design the end-to-end workflow, including which other systems such as Microsoft 365 or your CRM should be involved and where people must approve changes.
Testing and launch
We test the workflow against real past examples, then launch with monitoring and audit logs so you can see every action Claude takes.
Team training
We train your staff on how to make requests, review outputs and handle exceptions, so the new process is adopted with confidence.
Who benefits
- Operations managers
- Consistent task lists and fewer dropped actions across teams.
- Team leaders and project managers
- Meeting follow-ups turned into owned, dated tasks without manual data entry.
- HR and onboarding teams
- Standard checklists created reliably for every new starter.
- Executives and senior staff
- Clearer personal priorities and reminders with less administrative effort.
Security and control
- Access is limited to the specific lists and actions your organisation approves, following least-privilege principles.
- Sign-in uses OAuth, the standard method supported by Microsoft To Do.
- People approve consequential changes before they are made where your process requires it.
- Activity is logged so every action can be reviewed and audited.
- Workflows are tested on real past cases before launch and monitored afterwards.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can set up Claude workflows that align with their local data protection requirements. In India, workflows are designed to meet the Digital Personal Data Protection Act, 2023. Businesses in the UAE and Saudi Arabia are supported under their respective data protection laws. Hosting region is chosen during design to meet your specific compliance requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Microsoft To Do MCP server do?
The MCP server acts as a secure bridge between Claude and Microsoft To Do. It lets Claude read lists and tasks and take permitted actions, such as creating tasks, updating checklist items and setting reminders. The organisation decides what Claude can access, and the server works within those limits.
Is connecting Microsoft To Do to Claude secure?
Security depends on the setup. Sign-in uses OAuth, the standard method Microsoft To Do supports. Access is restricted to approved lists and actions, changes can require human approval, and activity is logged. We never guarantee outcomes, but we design each connection with these controls in place.
What can Claude do with Microsoft To Do once connected?
Typically, Claude can create tasks from requests, manage task lists, update checklist items and set reminders or due dates. People can give instructions in natural language, such as asking for a follow-up to be added to a named list by a specific date.
How long does setup take?
Timelines depend on the number of lists, the workflows involved and the other systems to connect. A focused single-team workflow is often quicker to launch than a multi-team process. We confirm the timeline during the free automation audit.
What permissions or plan do we need?
Generally, you need an account that can sign in to Microsoft To Do and grant the access the workflow requires. The exact permissions depend on your organisation's Microsoft setup, which we review during the audit so that access stays limited to what is needed.