SharePoint MCP Server

📑 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.gitcd 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-idSHP_ID_APP_SECRET=your-azure-app-secretSHP_TENANT_ID=your-tenant-idSHP_SITE_URL=https://your-tenant.sharepoint.com/sites/your-siteSHP_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 Inspectornpx @modelcontextprotocol/inspector -- sharepoint-mcp
# ▶️ Run directlysharepoint-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 repositorygit clone https://github.com/ravikant1918/sharepoint-mcp.gitcd sharepoint-mcp
# Step 2: Create .env file with your SharePoint credentialscp .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 runningdocker compose pscurl http://localhost:8000/health
# View logsdocker compose logs -f
# Stop containerdocker 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 variableSHAREPOINT_MCP_VERSION=v1.0.1 docker compose up -d
# Or add to .env fileecho "SHAREPOINT_MCP_VERSION=v1.0.1" >> .envdocker 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 setupgit clone https://github.com/ravikant1918/sharepoint-mcp.gitcd sharepoint-mcpcp .env.example .env# Edit .env with your credentials
# Step 2: Build from local Dockerfile and startdocker compose up -d --build
# Step 3: Rebuild after code changesdocker compose downdocker 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 imageSHAREPOINT_MCP_IMAGE=myusername/sharepoint-mcp \SHAREPOINT_MCP_VERSION=dev \docker compose up -d
# Or add to .envecho "SHAREPOINT_MCP_IMAGE=myusername/sharepoint-mcp" >> .envecho "SHAREPOINT_MCP_VERSION=dev" >> .envdocker compose up -d

What happens: Pulls from your custom registry/repository.

🔧 Common Commands

# Start in detached modedocker compose up -d
# Start with live logsdocker compose up
# View logsdocker compose logs -f
# Stop containerdocker compose down
# Restart containerdocker compose restart
# Pull latest imagedocker compose pull
# Rebuild and restartdocker 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"    }  }}

3. 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"      }    }  }}

🛠️ All 14 Tools

📁 Folder Management

📄 Document Management

🏷️ Metadata Management

⚙️ Full Configuration Reference

⚠️ Limitations

🔧 Troubleshooting

Authentication Errors

Problem: Missing or invalid SharePoint credentials
Solution: Verify all 4 required environment variables are set:

echo $SHP_ID_APP $SHP_ID_APP_SECRET $SHP_TENANT_ID $SHP_SITE_URL

Connection Issues (HTTP Transport)

Problem: Agent can't connect to the MCP server
Solution:

1. Ensure the server is running: curl http://localhost:8000/mcp/
2. Check the URL ends with /mcp/ (trailing slash required)
3. Verify the port is not blocked by a firewall

Docker Container Unhealthy

Problem: podman ps / docker ps shows (unhealthy)
Solution: Check container logs for errors:

docker logs sharepoint-mcp

Debug Logging

Enable verbose output by setting LOG_LEVEL=DEBUG:

LOG_LEVEL=DEBUG sharepoint-mcp

For Docker, add to your .env file or docker-compose.yml:

LOG_LEVEL=DEBUGLOG_FORMAT=console

Permission Errors

Problem: Access denied from SharePoint
Solution:

1. Verify the Azure AD app has the required API permissions
2. Ensure admin consent has been granted (if required by your org)
3. Confirm SHP_SITE_URL points to a site your app has access to

🧪 Development

git clone https://github.com/ravikant1918/sharepoint-mcp.gitcd sharepoint-mcppip install -e ".[dev]"
make test      # run all testsmake inspect   # 🔍 launch MCP Inspectormake check     # quick import sanity checkmake clean     # 🧹 remove caches

📚 Documentation

🤝 Contributing

Contributions are welcome! Please read docs/contributing.md and our Code of Conduct.

1. 🍴 Fork the repo
2. 🌿 Create a branch: git checkout -b feat/my-tool
3. ✅ Add tests: make test
4. 📬 Open a Pull Request

🔒 Security

Found a vulnerability? Please do not open a public issue.
Report privately via GitHub Security Advisories or see SECURITY.md.