Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect SharePoint to Claude Code

Let Claude update documents and manage lists in SharePoint. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect SharePoint to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect SharePoint, you add a SharePoint MCP server: a small hosted service that exposes SharePoint's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own SharePoint account. No API keys pasted into config files.

claude mcp add --transport http sharepoint https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in SharePoint once connected?

Full read-write SharePoint access lets Claude update a document in its library, add and edit list items, move or organize files across folders, set metadata, and post to a team site once you approve. The document upkeep and list maintenance that used to mean download, edit, and re-upload happen where the content already lives.

  • Update the contents of a document in a SharePoint library
  • Add, edit, or remove items in a SharePoint list
  • Move or copy files between folders and libraries
  • Set or correct metadata and columns on library files
  • Upload a new file into the right library after you approve
  • Search a site and propose batched edits across matching files

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same SharePoint access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the SharePoint API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when SharePoint changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build SharePoint connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same SharePoint connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own SharePoint account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on SharePoint's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to SharePoint?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the SharePoint account it signs in with. Revoking access is one click in SharePoint.

More on the SharePoint connector

SharePoint connector for claude.aiGoogle Drive + Claude CodeDropbox + Claude CodeBox + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us