6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Anthropic’s connector for SharePoint, OneDrive, Outlook and Teams.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Microsoft 365 MCP server searches SharePoint, OneDrive, Outlook and Teams from an AI assistant. Anthropic built and hosts it against Microsoft Graph — Microsoft did not ship it. Its seven listed tools all read. Writing email, calendar events and files is a separate surface your Microsoft Entra administrator must consent to before it exists at all.
Verified connector
Listed by Anthropic as an Anthropic-built connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
160.79.104.0/21, so such policies block every member until the range is excluded — an exclusion Anthropic warns should never be applied to a device compliance policy.No. Anthropic built and operates it. The directory lists Anthropic as the author, the endpoint sits on microsoft365.mcp.claude.com, and Anthropic's own security guide calls it an Anthropic-hosted integration and a secure proxy. Microsoft's role is the identity provider and the Graph API underneath. Anthropic states it completed Microsoft's publisher verification for the two app registrations.
Only after a Microsoft Entra Global Administrator consents to write scopes and an admin turns write tools on. Anthropic's documentation states that without that step the integration is read-only. With write tools enabled it can send email, manage drafts and calendar events, update mailbox settings, and create and update files in OneDrive and SharePoint.
Anthropic documents roughly twenty-eight delegated Graph permissions. The read set covers mail, calendar, Teams chat and channels, meeting recordings and transcripts, OneDrive and SharePoint files, and basic profiles of everyone in the directory. The write set adds five: Mail.Send, Mail.ReadWrite, Calendars.ReadWrite, Files.ReadWrite.All and MailboxSettings.ReadWrite, each consented separately.
Yes, at four levels. No one in a tenant can connect until an Entra Global Administrator grants one-time consent. Admins can set Assignment required on both enterprise applications to limit it to named groups, revoke individual Graph permissions to disable whole product areas, and on Team and Enterprise plans a Claude organization Owner must separately enable it.
Yes, the ones you can already read. Anthropic documents Chat.Read, ChatMessage.Read and ChannelMessage.Read.All among the requested delegated permissions, and chat_message_search searches Teams chat. Access mirrors your own Microsoft 365 permissions, so a private channel you are not a member of stays out of reach. Teams is read-only in both directions — no tool posts.
No. Anthropic states the connector requires a Microsoft Entra tenant tied to a Microsoft Business plan, and that personal accounts such as outlook.com, hotmail.com and live.com cannot authenticate. Anyone trying gets an authentication error. The connector itself is available on every Claude plan, including Free — the gate is the Microsoft account type, not the Claude subscription.
It reads a single file, email or chat message identified by a URI, rather than searching for one. Anthropic's security guide lists its required permission as varying by resource type, so its reach is bounded by whichever Graph scopes your tenant actually consented to. Revoke Sites.Read.All and its SharePoint reads fail alongside the search tools.
Usually a Conditional Access sign-in frequency policy. Anthropic states that after you sign in, its servers exchange tokens on your behalf, and in its testing Entra sees those requests as coming from Anthropic's IP range 160.79.104.0/21 rather than your device or network. Location and sign-in frequency policies therefore hit the connector for everyone in the tenant.
documentation URL is .../12542951-enabling-and-using-the-microsoft-365-connector and redirects here; this is the final 200. Source for the permissions reference, admin consent paths, both service principal app IDs, the write-tools enablement steps, the Conditional Access troubleshooting and the attribution-header note · retrieved 2026-08-19POST of initialize against https://microsoft365.mcp.claude.com/mcp (2026-08-19) — HTTP 401 with a full WWW-Authenticate: Bearer challenge naming resource_metadata. This is what sets authVerified. No tool was called and no authentication was attempted · retrieved 2026-08-19GET on the same endpoint (2026-08-19) — HTTP 404, Access-Control-Allow-Methods: POST, OPTIONS · retrieved 2026-08-19https://microsoft365.mcp.claude.com/.well-known/oauth-protected-resource/mcp — HTTP 404 on 2026-08-19, the exact address the server's own challenge header advertises. The root and path-appended forms also 404 · retrieved 2026-08-19https://microsoft365.mcp.claude.com/.well-known/oauth-authorization-server and the same path with /mcp appended — both HTTP 200 on 2026-08-19, diffed against each other. Source for the Microsoft endpoints, the api://07c030f6-…/.default scope and the app ID correspondence · retrieved 2026-08-19prompt_names, auth_required posture, and no permissions field published at all — a third state distinct from "Read" and "Read and write") · retrieved 2026-08-16https://support.claude.com/robots.txt (retrieved 2026-08-19, HTTP 200) — User-agent: * with three Disallow rules covering error and template paths only, a one-second crawl delay, and no Content-Signal line. Every article cited above is permitted, and https://support.claude.com/llms.txt returns HTTP 200 listing them. Contrary to a prior note in this workstream, appending .md to an article URL on this Intercom help centre does work and is how all three articles were read · retrieved 2026-08-19Connect Microsoft 365 once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.