Files and knowledge
Microsoft SharePoint for AI agents.
Managed auth, ready-made tools.
Find sites, read and upload files, and work with SharePoint lists on behalf of each of your users.
About Microsoft SharePoint
With the Microsoft SharePoint connector, your agent works with the SharePoint sites each user can already open. It can find sites, browse and read files in document libraries, upload new files, and read or add items in lists, using only the tools your project allows.
Microsoft SharePoint is Microsoft’s service for team sites, document libraries and lists.
Tools
What your agent can do in Microsoft SharePoint.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Microsoft SharePoint connection.
-
Search sites
Readmicrosoft_sharepoint_search_sitesFind SharePoint sites the user can access by name.
-
List files
Readmicrosoft_sharepoint_list_filesList the files and folders in a document library.
-
Read a file
Readmicrosoft_sharepoint_get_fileGet a file's details and download its content.
-
Upload a file
Writemicrosoft_sharepoint_upload_fileUpload a file to a document library folder.
-
List items
Readmicrosoft_sharepoint_list_itemsList the items in a SharePoint list.
-
Create an item
Writemicrosoft_sharepoint_create_itemAdd a new item to a SharePoint list.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Microsoft SharePoint, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read sites and files, and switch off
microsoft_sharepoint_upload_fileso it can never add a file. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example document libraries but not lists. A call outside them is refused.
Get started
Connect Microsoft SharePoint
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Microsoft SharePoint
Each end user authorizes their own Microsoft SharePoint account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Microsoft SharePoint account, once. const connection = await agent200 .user("user_123") .connect("microsoft_sharepoint"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Microsoft SharePoint tools
Name the user, the model and the tools. The model decides which Microsoft SharePoint tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Find the latest pricing deck on the sales site", tools: ["microsoft_sharepoint"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Microsoft's own sign-in page. You never see or store their Microsoft password.
-
What access is requested
The scopes the connection needs, such as reading sites, reading files or writing files, listed on Microsoft's authorization screen. Users can remove the app later from their Microsoft account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Microsoft SharePoint connector and how to use it.
Connector: Microsoft SharePoint, through Agent200. In code: "microsoft_sharepoint". What it does: Find sites, read and upload files, and work with SharePoint lists on behalf of each of your users. Page: https://www.agent200.com/connectors/microsoft-sharepoint/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Microsoft SharePoint's own page, through the authorization link Agent200 returns. Never ask a user for a Microsoft SharePoint password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: microsoft_sharepoint_search_sites, microsoft_sharepoint_list_files, microsoft_sharepoint_get_file, microsoft_sharepoint_list_items. Write tools: microsoft_sharepoint_upload_file, microsoft_sharepoint_create_item. Name "microsoft_sharepoint" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/microsoft-sharepoint/framework/claude/ https://www.agent200.com/connectors/microsoft-sharepoint/framework/chatgpt/ https://www.agent200.com/connectors/microsoft-sharepoint/framework/claude-code/ https://www.agent200.com/connectors/microsoft-sharepoint/framework/muse/ https://www.agent200.com/connectors/microsoft-sharepoint/framework/grok-bot/ https://www.agent200.com/connectors/microsoft-sharepoint/framework/openai-dots/ https://www.agent200.com/connectors/microsoft-sharepoint/framework/claude-duet/ https://www.agent200.com/connectors/microsoft-sharepoint/framework/hermes-agent/ https://www.agent200.com/connectors/microsoft-sharepoint/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/microsoft-sharepoint.md
Guides
Use Microsoft SharePoint with the AI you build on.
Step-by-step setup for Microsoft SharePoint with a specific model, assistant or agent framework.
-
Microsoft SharePoint + Claude
How to connect Microsoft SharePoint to Claude
-
Microsoft SharePoint + ChatGPT
How to connect Microsoft SharePoint to ChatGPT
-
Microsoft SharePoint + Claude Code
How to connect Microsoft SharePoint to Claude Code
-
Microsoft SharePoint + Muse
How to connect Microsoft SharePoint to Muse
-
Microsoft SharePoint + Grok Bot
How to connect Microsoft SharePoint to Grok Bot
-
Microsoft SharePoint + OpenAI Dots
How to connect Microsoft SharePoint to OpenAI Dots
-
Microsoft SharePoint + Claude Duet
How to connect Microsoft SharePoint to Claude Duet
-
Microsoft SharePoint + Hermes Agent
How to connect Microsoft SharePoint to Hermes Agent
-
Microsoft SharePoint + OpenClaw
How to connect Microsoft SharePoint to OpenClaw
FAQ
Microsoft SharePoint and Agent200, answered.
Who handles the Microsoft SharePoint OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Microsoft SharePoint.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Microsoft SharePoint connection, never another user's. It cannot reach anything the user or Microsoft SharePoint has not authorized.
Can I limit what my agent can do in Microsoft SharePoint?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.