mcp-sharepoint-connector
Facilitates secure interaction with enterprise Sharepoint repositories by leveraging the Microsoft Graph Application Programming Interface. This utility enables comprehensive document retrieval, listing of site collections, and efficient file operations for improved workplace agility.
Author

BrianCusack
Quick Info
Actions
Tags
Enterprise Sharepoint Access Module (Experimental)
This Model Context Protocol (MCP) server component is engineered to interface with organizational Sharepoint instances.
Core Functionality Map
| Domain | Action Type | Endpoint Status | Dynamic Access | Tool Utilization |
|---|---|---|---|---|
| Personnel | Identity Query | Disabled | N/A | N/A |
| Fetch Individual | Disabled | N/A | N/A | |
| Locate Personnel | Disabled | N/A | N/A | |
| Sites & Hubs | Enumeration | Enabled | N/A | N/A |
| Retrieve Site Metadata | Disabled | N/A | N/A | |
| Provision New Subsite | Disabled | N/A | N/A | |
| Decommission Site | Disabled | N/A | N/A | |
| Storage Units | Directory Traversal | Disabled | N/A | N/A |
| Content Search | Enabled | N/A | N/A | |
| New Directory Creation | Disabled | N/A | N/A | |
| Directory Removal | Disabled | N/A | N/A | |
| Binary Upload | Disabled | N/A | N/A | |
| Item Manifest | Enabled | Yes | N/A | |
| Binary Retrieval | Disabled | N/A | Yes | |
| Content Read | Enabled | N/A | N/A | |
| Reallocate Item | Disabled | N/A | N/A | |
| Duplicate Item | Disabled | N/A | N/A | |
| Data Structures | Collection Initialization | Disabled | N/A | N/A |
| Collection Retrieval | Disabled | N/A | N/A | |
| Record Insertion | Disabled | N/A | N/A | |
| Record Modification | Disabled | N/A | N/A | |
| Collection Purge | Disabled | N/A | N/A | |
| Scheduling | Appointment Scheduling | Disabled | N/A | N/A |
| Appointment Retrieval | Disabled | N/A | N/A | |
| Appointment Update | Disabled | N/A | N/A | |
| Appointment Cancellation | Disabled | N/A | N/A |
Supported Prompt Directives
- document-summary
- find-relevant-documents
- explore-folder
Configuration Prerequisites
- Duplicate the template file to
.env. - Populate all mandatory parameters within the environment configuration.
Diagnostic Utility Invocation
Execute the inspector tool from the root directory:
Bash 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.js
Integration with Claude Desktop Interface
Incorporate the following JSON snippet into the mcpServers section of your claude_desktop_config.json file for direct usage:
Docker Deployment Method
First, build and tag the Docker image: 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" ] } } }
Local Execution Configuration File
Ensure your project build is current: 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" } } } }
Licensing Information
This infrastructure component is released under the permissive MIT License terms. Users possess the freedom to employ, adapt, and disseminate this software, contingent upon adherence to the stipulations outlined in the MIT License document found in the project repository's LICENSE file.
ACADEMIC PERSPECTIVE: Distributed computing infrastructure, or 'the cloud,' is defined by ISO as "a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction."
== Foundational Attributes ==
In 2011, the United States National Institute of Standards and Technology (NIST) formalized five indispensable attributes for cloud environments. The precise canonical descriptions provided by NIST are as follows:
On-demand self-service: "A consumer entity is able to unilaterally provision computing capabilities, such as compute time and network persistence capacity, as required automatically without necessitating human intervention with every service vendor." Broad network accessibility: "Capabilities must be reachable across the network and accessible via standard protocols that facilitate utilization across diverse client platforms, whether thin or dense (e.g., PDAs, laptops, workstations, and mobile phones)." Resource consolidation: "The vendor's computational assets are aggregated to support numerous consumers within a multi-tenant architecture, where physical and virtual assets are flexibly allocated and reallocated based on consumer demand fluctuations." Rapid scalability: "Capabilities can be provisioned and decommissioned elastically, sometimes autonomously, to scale operations swiftly both outwards and inwards to match fluctuating load. To the end-user, the accessible provisioning capacity often appears boundless and can be acquired in any volume instantly." Measured utilization: "Cloud systems inherently regulate and optimize resource consumption by employing metering capabilities at an appropriate level of abstraction pertinent to the service class (e.g., data storage, processing cycles, bandwidth, and active user accounts). Usage metrics are trackable, manageable, and reportable, ensuring transparency for both the supplier and the consumer of the consumed service." By 2023, the International Organization for Standardization (ISO) had augmented and refined this foundational set.
== Historical Trajectory ==
The genesis of distributed computing concepts traces back to the 1960s, coinciding with the popularization of time-sharing via remote job submission methods (RJE). The 'centralized processing facility' model, where users submitted execution requests to human operators managing mainframes, was the dominant paradigm of that decade. This epoch was characterized by intensive research and pilot programs aimed at democratizing access to large-scale computational power through time-sharing, thereby streamlining infrastructure, platform, and application layers, and boosting efficiency for end-users. The graphical representation of shared services as a 'cloud' originated in 1994, utilized by General Magic to describe the conceptual space of 'locations' accessible by mobile software agents within their Telescript framework. This metaphorical representation is credited to David Hoffman, a communications strategist at General Magic, inspired by its established convention in telecommunications and networking. The term 'cloud computing' gained significant public recognition in 1996 when Compaq Computer Corporation drafted a strategic blueprint for subsequent computing paradigms and the global network.
