SharePoint
Connect agents to SharePoint for document management and collaboration. Access sites, lists, and documents.
Available Tools
12 tools available in this integration
Sharepoint.GetListsFromSite Retrieve lists from a SharePoint site
Sharepoint.GetItemsFromList Retrieve items from a list in a SharePoint site
Sharepoint.GetPage Retrieve metadata and contents of a page in a SharePoint site
Sharepoint.ListPages Retrieve pages from a SharePoint site
Sharepoint.GetSite Retrieve information about a specific SharePoint site
Sharepoint.SearchSites Search for SharePoint sites by name or description
Sharepoint.ListSites List all SharePoint sites accessible to the current user
Sharepoint.GetFollowedSites Retrieve a list of SharePoint sites followed by the current user
Sharepoint.GetDrivesFromSite Retrieve drives / document libraries from a SharePoint site
Sharepoint.ListRootItemsInDrive Retrieve items from the root of a drive in a SharePoint site
Sharepoint.ListItemsInFolder Retrieve items from a folder in a drive in a SharePoint site
Sharepoint.SearchDriveItems Search for items in one or more SharePoint drives
Why agent-optimized tools matter
Built for intent, not API schemas
Forcing the agent to juggle not only what you want to get done, but also how to operate all the APIs it needs to use is a recipe for disaster. Agent-optimized tools keep the agent focused on the work at hand, not ID hunting.
Up to 100x fewer tokens
Context bloat is a serious problem that gets in the way of real work getting done with agents. Agent-optimized tools return only the fields the agent needs to get the job done, not the full API response. Up to 100x less token consumption on every call.
Coverage for the whole task
Most tasks take more than one action to finish. Agent-optimized tools cover the full sequence so the agent completes the workflow end to end, not just the first lookup.
Consistent at scale
Agent-optimized tools behave the same across every user, every run, every harness, every model, and every effort level. No need for the agent to spend time and tokens re-learning the API shape, it can focus on the task at hand. What works for one user holds up when serving thousands in production.
Your questions, answered
It's built around what an agent is trying to accomplish rather than mirroring SharePoint's raw API. Fewer required parameters, far fewer tokens per call, and coverage for the whole task — so agents succeed more often.
Yes. The toolkit is exposed over an MCP gateway that any framework or MCP client can connect to, and we publish install guides for the editors and coding agents we document.
No. Arcade proxies API calls and does not persist your SharePoint content. Where SharePoint requires credentials, Arcade brokers them and stores them encrypted at rest — the model never sees them.
With Contextual Access policies: require human approval before consequential actions, redact sensitive fields on the way back, or restrict the scopes a given agent gets.
