# OneDrive & SharePoint

> Search, read, and write OneDrive and SharePoint files from an AI agent — official Microsoft remote MCP.

[Canonical HTML page](https://top-mcps.com/mcp/onedrive) · [server.json](https://top-mcps.com/mcp/onedrive.json) · [methodology](https://top-mcps.com/about/methodology)

## At a glance

- **Maintainer:** Microsoft
- **Transport:** Streamable HTTP
- **Auth model:** OAuth 2.1
- **Required secrets:** None
- **Supported clients:** VS Code, VS Code Insiders, Any MCP-compatible client supporting remote MCP
- **License:** Proprietary
- **Latest version:** latest
- **Last verified:** 2026-06-15
- **GitHub stars:** 3,212 (fetched 2026-06-22T06:16:39.659Z)
- **Score:** 79/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/microsoft/mcp

## Security & scope

- **Access scope:** read-write
- **Sandbox:** Hosted by Microsoft and authenticated via Microsoft Entra. The agent's scope equals the calling user's OneDrive and SharePoint permissions inside the tenant. Conditional-access policies apply.
- **Gotchas:**
  - The remote URL embeds the tenant ID — sharing a configured install bundle leaks tenant identity; use the install button rather than passing a raw URL.
  - Auto-discovered tools mean the available surface changes as Microsoft ships new Graph capabilities — review the latest tool list before relying on a specific call in an automation.

## Quick answer

**What it does.** Exposes Microsoft Graph OneDrive and SharePoint file operations as MCP tools that are auto-discovered from the ODSP endpoint — list and search drives, read and write files, navigate sites and document libraries, and run cross-content search across the tenant.

**Best for:**
- Microsoft 365 file search across OneDrive + SharePoint
- Reading a SharePoint document into the agent's context
- Writing generated files to a user's OneDrive
- Tenant-scoped, Entra-enforced installs
- Workflows that need conditional-access policies respected

**Not for:**
- Non-Microsoft-365 tenants
- Clients without remote-MCP support
- App-level (non-delegated) automation pipelines
- Workflows that need a feature outside the Graph files surface

## Recipes

### Summarise a SharePoint document into a Teams-ready brief

```
Search SharePoint for the most recent file named "Q4 launch plan" in the Marketing site, read it, and return a 5-bullet summary I can paste into a Teams channel.
```

_Tested with: VS Code_

## Description

The official Microsoft OneDrive & SharePoint (ODSP) remote MCP server gives an AI agent Microsoft-Graph-backed access to a tenant's OneDrive and SharePoint files. It is hosted by Microsoft at `agent365.svc.cloud.microsoft/agents/tenants/{tenant_id}/servers/mcp_ODSPRemoteServer` and authenticates against Microsoft Entra — the same identity layer the rest of Microsoft 365 uses. Tools are auto-discovered from the ODSP endpoint, so the surface tracks Graph as it ships new file capabilities.

## Why it matters

OneDrive and SharePoint are the default file surface for Microsoft 365 customers — for many enterprises they are the file system. The official Microsoft MCP is the only path that respects existing Entra identity, tenant boundaries, and conditional-access policies; community connectors using app-level tokens bypass that, which is a non-starter for IT.

## Key features

- Hosted by Microsoft at `agent365.svc.cloud.microsoft` — no install
- Microsoft Entra auth — inherits tenant identity and conditional access
- Tools auto-discovered from the ODSP MCP endpoint
- Listed in github.com/microsoft/mcp (official catalog)
- One-click install into VS Code and VS Code Insiders

## FAQ

### Where is the install URL documented?

In the official Microsoft MCP catalog at github.com/microsoft/mcp. The remote URL includes the tenant ID — copy it from the catalog page (the VS Code / VS Code Insiders install buttons substitute the ID for you).

### Does it work with Claude or Cursor?

The official install buttons in the Microsoft catalog target VS Code and VS Code Insiders. Other MCP-compatible clients can connect by adding the remote URL manually, as long as they support remote MCP and the Entra OAuth flow.

### What does it authenticate against?

Microsoft Entra (formerly Azure AD). The agent inherits the calling user's tenant identity and any conditional-access policies the tenant enforces. Token rotation happens through Entra, not the MCP.

### Is there an Anthropic-built or community Microsoft 365 MCP?

There are several community OneDrive/SharePoint MCPs (`ftaricano/mcp-onedrive-sharepoint`, `Aanerud/MCP-Microsoft-Office`, `pnp/cli-microsoft365-mcp-server`). They are useful for personal-account flows, but for tenant-grade installs the official Microsoft remote MCP is the right default — it is the only one with first-party Entra enforcement and Microsoft support.

## Changelog

- **2026-06-15** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-11-12** — Initial directory listing.