Think inside your AI world.
How do I connect Microsoft 365 to Claude?
The Microsoft estate reaches assistants over MCP: SharePoint and OneDrive files, Outlook mail and calendar, Teams chat search — scoped by what you authorise.
Direct answer: Microsoft 365's MCP surface covers SharePoint, OneDrive, Outlook and Teams — with Teams chat search and sync indexing documented, and Outlook Calendar noted read-only in OpenAI's ecosystem. In Claude: Settings → Connectors, add the connector and authorise your Microsoft account; Claude Code takes 'claude mcp add'. Scopes follow your grant, and for a first connection the read-shaped slice is the sensible one.
One estate, several surfaces
The proposal on SharePoint, the thread in Teams, the meeting in Outlook — one authorisation chain puts the working estate in reach. For organisations living in Microsoft, this single connection carries more daily questions than any other on this site.
Teams talks; someone must settle
Worked case: your team ratified a Teams-decisions rule — anything decision-shaped in a Teams thread gets ratified or explicitly parked within a day, because an unratified 'let's go with the cheaper vendor' once ran for six weeks as policy nobody had actually made. Teams preserves the sentence; your one-day settling window is governance you added above the chat.
Through Unl the thread read arrives with the window running: yesterday's decision-shaped message about the pricing page — unratified and unparked, eighteen hours in, the accidental-policy story attached. Chat stays fast; standing stays deliberate.
Microsoft 365 to Claude puts the working estate in reach; through Unl the estate answers to the settling disciplines you ratified — decision-shaped chat gets settled or parked on your clock.
Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. The reach lane is live: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.
Read further
Questions people ask
What parts of Microsoft 365 are readable over MCP?
SharePoint and OneDrive files, Outlook (calendar noted read-only in OpenAI's ecosystem), and Teams chat search with sync indexing — per the scopes you authorise.
Is this an official Microsoft integration?
The MCP surface follows Microsoft's ecosystem documentation; check the current connector listing at setup, as the estate's coverage evolves. This page mirrors what is documented, nothing more.
What rules suit a Microsoft-centric team?
Settling windows for Teams, current-template rules for SharePoint, commitment capture for Outlook — the same governance patterns, applied to the estate where your org actually works.
What if a thread is neither settled nor safely parked?
Then it stays open and the clock keeps counting, which is uncomfortable and accurate. The failure is parking things to clear the list. A park with no review date is an abandonment wearing a decision's clothes, and the clock is what tells the two apart.
What this is
Think inside your AI world — you stay in command
Save the thoughts, decisions and targets worth keeping, each with its reasoning, carried into every AI session the moment they matter. A new unit of exchange between you and your AI: the Settled Why with standing that travels. Unprompted.
Your whole AI world. What you decided at the epicentre. It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector — quick to connect, in a couple of steps.
MCP native·Human settled·Model agnostic·Your data
Measured Context
Connect Unl to bring the right information into the moment.
Your sources, read against the criteria you set.
The full product, open. Free at launch.