Microsoft SharePoint MCP Tools for AI Agents
Let an agent find SharePoint sites and files, read Word documents and slides, update Excel cells, and create or organize content.
Available Tools
52 tools available in this integration
Why agent-optimized tools matter
Built for intent, not API schemas
Ask the agent to "find the project site, read the latest policy page, and add a summary to a Word document." Arcade picks the right SharePoint tools without guessing site, drive, or item IDs.
Up to 100x fewer tokens
SharePoint search and folder listings return item metadata first and fetch document, slide, or cell content only when asked, so the agent avoids loading whole libraries into the model.
Complete the workflow end to end
Find the site, locate the library, read the source, update a workbook, and create a share link through one toolkit designed around the complete SharePoint task.
Make actions predictable and controlled
Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.
Securing Microsoft SharePoint
The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.
This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.
For Microsoft SharePoint, you can implement some of these policies:
Access
- Hide MicrosoftSharepoint.DeleteItem from agents unless the roles your IDP marks as SharePoint owners are active, so regular users cannot remove files or folders.
- Restrict MicrosoftSharepoint.CreateShareLink to agents operating under your document-sharing role, so unapproved automation cannot expose internal files through new links.
- Deny MicrosoftSharepoint.MoveItem to agents outside your content-management role, so they cannot move files into restricted or public folders.
- Hide MicrosoftSharepoint.TrashItems from agents unless the roles your IDP marks as site administrators are active, so regular users cannot send shared files or folders to the recycle bin.
- Restrict MicrosoftSharepoint.MoveItems to agents operating under your content-operations role, so automation cannot relocate batches of files into folders with broader access.
- Deny MicrosoftSharepoint.SetSlideNote to agents outside your presentation-owner role, so they cannot alter speaker notes in an approved executive or customer presentation.
Pre-execution
- Require human approval before MicrosoftSharepoint.UpdateRange changes a workbook used for financial, payroll, or production reporting, so an agent cannot overwrite multiple business-critical cells without review.
- Block MicrosoftSharepoint.InsertTextAtEndOfWordDocument when the target document is marked legal, contractual, or approved, so an agent cannot append unreviewed language to a controlled record.
- Require human approval before MicrosoftSharepoint.DeleteWorksheet runs, so an agent cannot remove a worksheet containing source data or audit history.
- Require human approval before MicrosoftSharepoint.AddTextToWordDocument changes a document marked final, legal, or contractual, so an agent cannot add unreviewed language to an approved record.
- Block MicrosoftSharepoint.CreateWorksheet when the workbook belongs to your financial, payroll, or regulatory reporting libraries, so an agent cannot introduce unreviewed tabs into controlled workbooks.
- Require human approval before MicrosoftSharepoint.UpdateWorksheet renames a worksheet used by scheduled reports, so an agent cannot break downstream references with an unchecked name change.
Post-execution
- Redact MicrosoftSharepoint.GetWordDocument results by removing personal phone numbers, home addresses, access tokens, and secrets before the document content reaches the model.
- Strip customer names, confidential project details, and speaker notes containing internal strategy from MicrosoftSharepoint.GetPresentationAsMarkdown results before the model sees the presentation.
- Redact MicrosoftSharepoint.GetWorksheetData results by masking employee tax IDs, bank details, compensation, and other payroll fields before they reach the model.
- Redact MicrosoftSharepoint.DownloadFileText results by removing account numbers, access tokens, personal addresses, and other secrets before file text reaches the model.
- Strip MicrosoftSharepoint.GetSlideNote results containing customer details, internal strategy, or speaker-only commentary before the model sees the note.
- Deny MicrosoftSharepoint.ListFolderItems results for folders marked confidential or under legal hold, so the model cannot infer restricted filenames, paths, or document metadata.
How to use Microsoft SharePoint with your agent
Connect Microsoft SharePoint to your MCP client through Arcade, then authorize each user's SharePoint account. The walkthrough takes you from setup to your first site search or document update.
Your questions, answered
A Microsoft SharePoint MCP server exposes SharePoint sites, document libraries, lists, pages, files, Word documents, Excel workbooks, and PowerPoint presentations as structured tools an AI agent can call through the Model Context Protocol. After a user authorizes their account, the agent can perform the permitted read and write actions.
Microsoft SharePoint's native APIs are not an MCP server. Arcade exposes SharePoint actions through MCP and adds per-user OAuth, approval workflows, response redaction, and scope controls so the same integration works across supported clients and frameworks.
Arcade agents can find sites, libraries, folders, files, lists, and pages; read Word, PDF, text, PowerPoint, and Excel content; create and edit Word documents, workbooks, worksheets, presentations, slides, and speaker notes; move, copy, rename, share, or delete items; and update list or worksheet data.
Arcade requests the delegated Microsoft Graph and SharePoint permissions required by the actions you enable. Read-only workflows need read access to the relevant sites, drives, lists, pages, and files; creating, editing, moving, sharing, or deleting content requires the corresponding write or delete permissions, subject to tenant consent and the user's SharePoint access.
Yes. Each user authorizes their own Microsoft account through OAuth. SharePoint actions run under that user's authorization and can reach only the sites, libraries, lists, and files that user is allowed to access.
Yes. Contextual Access policies can require human approval before consequential SharePoint actions such as deleting or trashing items, moving files, creating share links, or changing documents and workbook data. The call proceeds only after the policy's conditions have been satisfied.
Arcade proxies SharePoint API calls and does not persist your content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives raw credentials.
Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.
Arcade refreshes access while the user's Microsoft authorization remains valid. If it is revoked, rotated, or can no longer be refreshed, SharePoint actions stop until the user reconnects their account.
Microsoft Graph throttling and SharePoint service limits still apply to calls made through Arcade. High-volume listing, searching, file operations, and workbook updates may be throttled, so clients should honor retry responses and avoid unnecessary repeated reads.