SharePoint MCP Server

🗂️ sharepoint-mcp

The MCP Server that gives your AI agent a brain for Microsoft SharePoint

A production-grade Model Context Protocol (MCP) server for Microsoft SharePoint. Connect Claude Desktop, VS Code Copilot, Cursor, Continue, or any MCP-compatible AI agent to your SharePoint — read files, manage folders, and reason over your organisation's knowledge.

📚 Docs · 🗺️ Roadmap · 🐛 Bugs · 💡 Features

---

📑 Table of Contents

• Why sharepoint-mcp?
• What Your Agent Can Do
• Features
• Quickstart
• Docker
• Transport Modes
• Integrations — Claude Desktop · VS Code Copilot · Cursor
• All 14 Tools
• Configuration Reference
• Limitations
• Troubleshooting
• Development
• Documentation
• Contributing
• Security

---

🧠 Why sharepoint-mcp?

Most AI agents only know what's in their training data.

sharepoint-mcp gives your agent _live access_ to your organisation's real knowledge.

---

🚀 What Your Agent Can Do

📖 Understand Any Document

You: "Summarise the Q3 report in the Finance folder"

Agent: → Get_Document_Content("Finance", "Q3_Report.pdf") → Reads full extracted text → Returns a sharp, accurate summary

✏️ Read → Reason → Write

You: "Translate the proposal to French and save it"

Agent: → Get_Document_Content → translate → Upload_Document

🗂️ Navigate Your Library

You: "What files are in the Legal/Contracts folder?"

Agent: → List_SharePoint_Documents("Legal/Contracts")

📊 Supported File Formats

---

✨ Features

---

⚡ Quickstart

1️⃣ Install

pip install sharepoint-mcp

Or from source:

git clone https://github.com/ravikant1918/sharepoint-mcp.git

cd sharepoint-mcp && pip install -e .

2️⃣ Configure

cp .env.example .env

Open .env and fill in your Azure AD credentials

SHP_ID_APP=your-azure-app-client-id

SHP_ID_APP_SECRET=your-azure-app-secret SHP_TENANT_ID=your-tenant-id SHP_SITE_URL=https://your-tenant.sharepoint.com/sites/your-site SHP_API_TYPE=office365 # or "graph" / "graphql" for Microsoft Graph API

🔑 New to Azure AD? Follow the step-by-step guide →

🔀 Choose Your API: SharePoint MCP supports both Office365 REST API (default) and Microsoft Graph API. See API Configuration Guide →

Optional: Scope to a subfolder

By default, the server accesses your entire document library root. To restrict operations to a specific subfolder:

# Only operate within this subfolder (omit for full library access)

SHP_DOC_LIBRARY=mcp_server

Library name (only needed if your org renamed "Shared Documents")

Graph API auto-detects the default drive — this is only for Office365 REST API

SHP_LIBRARY_NAME=Shared Documents

3️⃣ Run

# 🔍 Interactive testing with MCP Inspector

npx @modelcontextprotocol/inspector -- sharepoint-mcp

▶️ Run directly

sharepoint-mcp

---

🐳 Docker

The fastest way to deploy for remote or cloud use.

📋 Usage Scenarios

Scenario A: Pull Latest Version from DockerHub (Recommended)

Use this for production deployments with the latest stable release:

# Step 1: Clone repository

git clone https://github.com/ravikant1918/sharepoint-mcp.git cd sharepoint-mcp

Step 2: Create .env file with your SharePoint credentials

cp .env.example .env

Edit .env and fill in:

SHP_ID_APP=your-app-id

SHP_ID_APP_SECRET=your-secret

SHP_TENANT_ID=your-tenant-id

SHP_SITE_URL=https://yourcompany.sharepoint.com/sites/yoursite

Step 3: Start container (pulls from DockerHub automatically)

docker compose up -d

Step 4: Verify it's running

docker compose ps curl http://localhost:8000/health

View logs

docker compose logs -f

Stop container

docker compose down

What happens: Pulls ravikant1918/sharepoint-mcp:latest from DockerHub with automatic architecture detection (Intel/ARM).

---

Scenario B: Use Specific Version

Lock to a specific version for stability or testing:

# Step 1: Set version via environment variable

SHAREPOINT_MCP_VERSION=v1.0.1 docker compose up -d

Or add to .env file

echo "SHAREPOINT_MCP_VERSION=v1.0.1" >> .env docker compose up -d

What happens: Pulls ravikant1918/sharepoint-mcp:v1.0.1 instead of latest.

---

Scenario C: Build Locally from Source

Use this for development or when you've made local code changes:

# Step 1: Clone and setup

git clone https://github.com/ravikant1918/sharepoint-mcp.git cd sharepoint-mcp cp .env.example .env

Edit .env with your credentials

Step 2: Build from local Dockerfile and start

docker compose up -d --build

Step 3: Rebuild after code changes

docker compose down docker compose up -d --build

What happens: Builds image from local Dockerfile, tags as ravikant1918/sharepoint-mcp:latest, and starts container.

---

Scenario D: Use Custom Image/Fork

If you've forked the repo and published to your own DockerHub:

# Use your custom image

SHAREPOINT_MCP_IMAGE=myusername/sharepoint-mcp \ SHAREPOINT_MCP_VERSION=dev \ docker compose up -d

Or add to .env

echo "SHAREPOINT_MCP_IMAGE=myusername/sharepoint-mcp" >> .env echo "SHAREPOINT_MCP_VERSION=dev" >> .env docker compose up -d

What happens: Pulls from your custom registry/repository.

---

🔧 Common Commands

# Start in detached mode

docker compose up -d

Start with live logs

docker compose up

View logs

docker compose logs -f

Stop container

docker compose down

Restart container

docker compose restart

Pull latest image

docker compose pull

Rebuild and restart

docker compose up -d --build

Remove everything (including volumes)

docker compose down -v

Using Podman? Just replace docker with podman — fully compatible.

Docker Environment Variables

---

🔌 Transport Modes

---

🔗 Integrations

🤖 Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{

"mcpServers": { "sharepoint": { "command": "sharepoint-mcp", "env": { "SHP_ID_APP": "your-app-id", "SHP_ID_APP_SECRET": "your-app-secret", "SHP_SITE_URL": "https://your-tenant.sharepoint.com/sites/your-site", "SHP_TENANT_ID": "your-tenant-id", "SHP_DOC_LIBRARY": "my-subfolder" } } } }

💡 Omit SHP_DOC_LIBRARY to access the full library root. If your org uses Office365 REST API and renamed the default library, also set SHP_LIBRARY_NAME.

💻 VS Code Copilot (Agent Mode)

1. Start the server via Docker or TRANSPORT=http sharepoint-mcp
2. Create .vscode/mcp.json in your workspace:

{

"servers": { "sharepoint": { "url": "http://localhost:8000/mcp/", "type": "http" } } }

1. Open Copilot Chat → switch to Agent mode → your 14 SharePoint tools are available.

⚠️ Trailing slash matters — the URL must end with /mcp/ (not /mcp).

⌨️ Cursor / Continue

Add to your MCP config (uses stdio transport):

{

"mcpServers": { "sharepoint": { "command": "sharepoint-mcp", "env": { "SHP_ID_APP": "your-app-id", "SHP_ID_APP_SECRET": "your-app-secret", "SHP_SITE_URL": "https://your-tenant.sharepoint.com/sites/your-site", "SHP_TENANT_ID": "your-tenant-id" } } } }

---