search-documents
Search query to find documents
LABSCO SUMMARY
Read-side access to a SharePoint drive, through your own app registration.
It is the narrow useful slice: find the folder, see what is in it, and pull a document back into the conversation — with the credentials scoped by the app registration you created rather than by a shared login.
What it is
A connector to organisational SharePoint through the Microsoft Graph credentials of an app registration. The repository's own implementation table is the honest map of it: sites, drives, lists and calendar are all sketched out, and a handful of the drive operations are the ones actually wired up.
What you get
- Search folders across the drive, and download a file
- Site listing and file reading exposed as resources, with drive items available as a dynamic resource
- Three prompts the client can call directly: document-summary, find-relevant-documents, explore-folder
Requirements
An Azure app registration with access to the site: TENANT_ID, CLIENT_ID and CLIENT_SECRET, plus the SITE_ID and DRIVE_ID you are pointing at — copy .env.example to .env and fill them in. Build with pnpm run build and run node, or docker build -t mcp/sharepoint . and pass the five values as -e flags. The README labels the project work in progress and for research at this stage, and its table marks the write operations — create folder, upload, move, copy, list and calendar CRUD — as not implemented.
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
01
Finding a document nobody can name
Search the drive's folders for the pattern you remember, then list what is inside the one that matches.
02
Summarising a document without downloading it first
Use the document-summary prompt against a file the server can read, so the summary comes back in the same conversation.
03
Exploring an unfamiliar team drive
The explore-folder prompt walks the structure so you learn where things live before asking for a specific file.
04
Pulling a file into a task
Download the item you located and hand its contents to whatever the assistant is doing next.
2 tools
Listed in project docs. Your client may show a different list.
download-document
The ID of the document to download
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- docker on PATH
- TENANT_ID in your environment
- CLIENT_ID in your environment
- CLIENT_SECRET in your environment
- SITE_ID in your environment
- DRIVE_ID in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Build the image from the repository, then point your client at it.
Server setup
TERMINAL
git clone https://github.com/BrianCusack/mcpsharepoint
cd mcpsharepoint
docker build -t mcp/sharepoint .Add the block below to your Claude Desktop config
MCP Clients
Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"sharepoint": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e",
"DOCKER_CONTAINER=true",
"-e",
"TENANT_ID=<YOUR_TENANT_ID>",
"-e",
"CLIENT_ID=<YOUR_CLIENT_ID>",
"-e",
"CLIENT_SECRET=<YOUR_CLIENT_SECRET>",
"-e",
"SITE_ID=<YOUR_SITE_ID>",
"-e",
"DRIVE_ID=<YOUR_DRIVE_ID>",
"mcp/sharepoint"
]
}
}
}
