Mcp Sharepoint

Created By
Sofias-aia year ago
A lightweight MCP Server for seamless integration with Microsoft SharePoint, enabling MCP clients to interact with documents, folders and other SharePoint resources. Developed by sofias tech
Overview

what is Mcp Sharepoint?

Mcp Sharepoint is a lightweight MCP Server designed for seamless integration with Microsoft SharePoint, allowing MCP clients to interact with documents, folders, and other SharePoint resources.

how to use Mcp Sharepoint?

To use Mcp Sharepoint, set up the server by registering an app in Azure AD, obtaining the necessary credentials, and configuring the environment variables. Then, run the server and use the provided tools to manage SharePoint resources.

key features of Mcp Sharepoint?

  • Clean interface for SharePoint resource management through the Model Context Protocol (MCP)
  • Tools for listing folders and documents, retrieving document content, creating and uploading documents, and deleting resources
  • Optimized operations for efficient document management

use cases of Mcp Sharepoint?

  1. Managing documents and folders in SharePoint for collaborative projects
  2. Automating document uploads and updates in SharePoint libraries
  3. Integrating SharePoint document management with other applications using MCP

FAQ from Mcp Sharepoint?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that facilitates interaction with resources in a structured manner, allowing for efficient management of documents and folders.

  • Is Mcp Sharepoint free to use?

Yes! Mcp Sharepoint is open-source and free to use under the MIT License.

  • What are the system requirements for running Mcp Sharepoint?

Mcp Sharepoint requires Python 3.10 or higher and the dependencies listed in the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Sofias-ai
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

4 hours ago
Gpt Scrambler

a day ago