The Sharepoint MCP Server provides access to Organizational Sharepoint with limited functionality for research and development purposes.
Capabilities:
List available Sharepoint sites
List items (files and folders) within a specific resource
Read file contents from Sharepoint
Download files using available tools
Search folders and documents using queries (with optional maxResults parameter)
Support for document-summary, find-relevant-documents, and explore-folder prompts
A Model Context Protocol server that provides access to Organisational Sharepoint.
Component | Operation | Resource | Dynamic Resource | Tool |
Users | ❌ | ❌ | ❌ | |
Read User | ❌ | ❌ | ❌ | |
Find User | ❌ | ❌ | ❌ | |
Sites | ❌ | ❌ | ❌ | |
List Sites | ✅ | ❌ | ❌ | |
Get Site Details | ❌ | ❌ | ❌ | |
Create Subsite | ❌ | ❌ | ❌ | |
Delete Site | ❌ | ❌ | ❌ | |
Drives | ❌ | ❌ | ❌ | |
List Folders | ❌ | ❌ | ❌ | |
Search Folders | ❌ | ❌ | ✅ | |
Create Folder | ❌ | ❌ | ❌ | |
Delete Folder | ❌ | ❌ | ❌ | |
Upload File | ❌ | ❌ | ❌ | |
List Items | ❌ | ✅ | ❌ | |
Download File | ❌ | ❌ | ✅ | |
Read File | ✅ | ❌ | ❌ | |
Move File | ❌ | ❌ | ❌ | |
Copy File | ❌ | ❌ | ❌ | |
Lists | ❌ | ❌ | ❌ | |
Create List | ❌ | ❌ | ❌ | |
Read List | ❌ | ❌ | ❌ | |
Add to List | ❌ | ❌ | ❌ | |
Update List | ❌ | ❌ | ❌ | |
Delete List | ❌ | ❌ | ❌ | |
Calendar | ❌ | ❌ | ❌ | |
Create Event | ❌ | ❌ | ❌ | |
Read Event | ❌ | ❌ | ❌ | |
Update Event | ❌ | ❌ | ❌ | |
Delete Event | ❌ | ❌ | ❌ |
document-summary
find-relevant-documents
explore-folder
Related MCP server: SharePoint MCP Server
Copy .env.example as .env
Fill the requires fields
From root
npx @modelcontextprotocol/inspector -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 -- node dist/index.jsTo use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your claude_desktop_config.json:
Docker build and tag docker build -t mcp/sharepoint .
{
"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"
]
}
}
}pnpm run build{
"mcpServers": {
"sharepoint": {
"command": "node",
"args": ["run", "start"],
"env": {
"TENANT_ID": "your-tenant-id",
"CLIENT_ID": "your-client-id",
"CLIENT_SECRET": "your-client-secret",
"SITE_ID": "your-site-id",
"DRIVE_ID": "your-drive-id",
}
}
}
}This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
| Name | Required | Description | Default |
|---|---|---|---|
| maxResults | No | Maximum number of results to return (as a string) | |
| query | Yes | Search query to find documents |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0search-documentsWith only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search-documents' has a distinct purpose that cannot be confused with any other tool in the set.
The naming is trivially consistent as there is only one tool. The tool name 'search-documents' follows a verb-noun pattern, which is clear and predictable, though this cannot be evaluated across multiple tools.
A single tool is too few for a server named 'Sharepoint MCP Server', which suggests a broader domain like document management, collaboration, or file handling. This minimal set likely leaves significant gaps in functionality, making it inappropriate for the apparent scope.
The tool set is severely incomplete for a Sharepoint domain. With only a search tool, there are obvious gaps in CRUD operations (e.g., create, update, delete documents), user management, or other typical Sharepoint functionalities, which will cause agent failures in handling common workflows.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.
Permissioned access to Outlook, OneDrive and Teams via the user's own Microsoft account
Securely search and manage workspace context files for AI agents and teams.
Provides metadata information to AI agents through the search API.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BrianCusack/mcpsharepoint'
If you have feedback or need assistance with the MCP directory API, please join our Discord server