SharePoint MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGLEVEL | No | Log level (e.g. DEBUG) | |
| SHP_ID_APP | No | Azure AD Application (client) ID | |
| SHP_SITE_URL | No | SharePoint site URL (e.g. https://contoso.sharepoint.com/sites/yoursite) | |
| SHP_CERT_PATH | No | Path to certificate file for certificate-based auth | |
| SHP_TENANT_ID | No | Azure AD Tenant ID | |
| SHP_AUTH_METHOD | No | Authentication method: msal (default), certificate, legacy | |
| SHP_DOC_LIBRARY | No | Document library name (default: Shared Documents) | |
| SHP_ID_APP_SECRET | No | Azure AD client secret | |
| SHP_CERT_THUMBPRINT | No | Certificate thumbprint for certificate-based auth |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| List_SharePoint_FoldersB | List all folders in a specified directory or root of the document library |
| List_SharePoint_DocumentsC | List all documents in a specified folder with metadata |
| Get_Document_ContentC | Get the content of a document (supports text extraction from PDF, Word, Excel, and text files) |
| Upload_DocumentC | Upload a new document to SharePoint |
| Update_DocumentB | Update the content of an existing document |
| Delete_DocumentB | Delete a document from SharePoint |
| Create_FolderC | Create a new folder in SharePoint |
| Delete_FolderB | Delete an empty folder from SharePoint |
| Get_SharePoint_TreeB | Get a recursive tree view of SharePoint folder structure |
| Test_ConnectionA | Test the SharePoint connection and authentication |
| Create_Word_DocumentA | Create a formatted Word document (.docx) with headings, paragraphs, tables, lists, images, hyperlinks, horizontal rules, and page breaks. Supports rich formatting including colors, highlighting, and spacing. Upload directly to SharePoint. |
| Edit_Word_DocumentA | Edit an existing Word document (.docx) with find/replace operations and SECTION REPLACEMENT for monthly status reports. Preserves all formatting. SIMPLE REPLACEMENT: Replace individual placeholders ({{company_name}} -> 'Acme Corp') SECTION REPLACEMENT FOR MONTHLY REPORTS: Replace entire sections (8 bullets, tables) in one operation.
USE CASES:
|
| Create_PowerPointB | Create a formatted PowerPoint presentation (.pptx) with multiple slide layouts, text boxes, bullet points, images, tables, shapes, and rich formatting. Upload directly to SharePoint. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SharePoint Document Library: Shared Documents | Main SharePoint document library configured for this server |
TDQS
Scored across 13 tools
Most tools have distinctly clear purposes, but 'Edit_Word_Document' and 'Update_Document' could be confused (both modify a document), and 'Upload_Document' overlaps partially with 'Create_Word_Document' and 'Create_PowerPoint'. However, detailed descriptions help differentiate them.
Tool names follow a verb_noun pattern, but the nouns vary in specificity (e.g., 'Create_PowerPoint' vs. 'Create_Word_Document', and 'List_SharePoint_Documents' vs. 'Get_Document_Content'). The mix of 'Get_', 'List_', 'Create_', 'Delete_', 'Edit_', 'Update_', 'Upload_', and 'Test_' is acceptable but lacks full consistency.
With 13 tools covering folder and document operations, plus connection testing and tree view, the count is well-scoped for a SharePoint integration. It provides essential functionality without being bloated or too sparse.
The tool set covers CRUD for folders and documents, with specialized creation for Word and PowerPoint. Gaps include inability to delete non-empty folders, lack of rename/move operations, and no search or permission management. These are minor but notable.