SharePoint
SharePoint is a Microsoft platform for document management and intranets, enabling teams to collaborate, store, and organize content securely and effectively
Verdict
Common use cases
- Provision project folders during kickoff calls
- Add tracking items to shared lists
- Verify user access before document handoff
- Audit who has permissions on sensitive sites
- Automate list creation for recurring workflows
Integration
- Vendor
- SharePoint
- Category
- docs
- Auth
- OAUTH2
- Tools
- 6
- Composio slug
share_point
Tools
- Create SharePoint Folder
Creates a new folder in sharepoint using the rest api.
- Create SharePoint List
Creates a new list in sharepoint using the rest api.
- Create SharePoint List Item
Creates a new item in a sharepoint list.
- Create SharePoint User
Creates a new user in sharepoint.
- Find SharePoint User
Finds a user in both microsoft graph and sharepoint to verify their existence and status.
- Remove SharePoint Userdestructive
Removes a user from sharepoint. will not fail if user doesn't exist.
Setup
Setup guide
- 11. In Switchy, open the Space where you want SharePoint access and click Integrations in the sidebar. 2. Find SharePoint in the catalog and click Connect. 3. You'll redirect to Microsoft's OAuth consent screen — sign in with an account that has SharePoint admin privileges. 4. Grant Sites.ReadWrite.All (to manage sites and lists) and User.ReadWrite.All (to look up and modify users). 5. After approving, you'll return to Switchy and see a green checkmark next to SharePoint. 6. Test the connection by typing '@SharePoint find user [your email]' in the Space chat — if it returns your profile details, you're live. 7. From now on, any @SharePoint mention in this Space invokes the MCP's tools directly in conversation.
What teammates see: by default, memories from SharePoint are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Project Folder
@SharePoint create a folder called 'Q2 Product Launch' in the Marketing site's Shared Documents library.Open in a Space →
Add List Item
@SharePoint add an item to the 'Support Requests' list with Title 'Login bug on mobile' and Priority 'High'.Open in a Space →
Check User Exists
@SharePoint find user jane.doe@company.com and tell me if she has an active SharePoint account.Open in a Space →
Provision New List
@SharePoint create a new list called 'Feature Requests' in the Product site with columns for Title, Requester, and Status.Open in a Space →
Remove User Access
@SharePoint remove user john.smith@company.com from SharePoint and confirm when it's done.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@SharePoint find user maria.santos@company.com and show me her current status and permissions
Found Maria Santos in both Microsoft Graph and SharePoint. Account status: Active. SharePoint permissions: Member of 'Marketing Team' site with Contribute access, Owner of 'Campaign Assets' library. Last activity: 2 days ago. Email verified, no pending invitations. This example shows a typical user lookup returning identity confirmation and permission scope across the tenant.
This read operation requires User.Read.All scope in Microsoft Graph and tenant-level SharePoint admin permissions. The MCP verifies the user exists in both systems before returning status — useful for auditing access before granting new permissions or troubleshooting login issues.
@SharePoint create a new list called 'Q1 Campaign Tracker' in the Marketing site with columns for Campaign Name, Owner, Budget, and Status
Created list 'Q1 Campaign Tracker' in the Marketing site at /sites/marketing/Lists/Q1CampaignTracker. Added 4 columns: Campaign Name (single line text), Owner (person/group), Budget (currency), Status (choice: Not Started, In Progress, Complete). List is now visible to all site members with Contribute permissions. This example demonstrates schema creation via the REST API without manual UI clicks.
Requires Sites.Manage.All permission and Contribute access to the target site. The MCP creates the list structure but does not populate initial items — you'll need a separate create-item call or bulk import. Be aware that SharePoint enforces column name character limits and reserved-word restrictions.
@SharePoint review all items in the 'Project Deliverables' list where Status is 'Overdue' and draft a summary email for the PM
Found 7 overdue items in 'Project Deliverables'. Summary: 3 items assigned to Design (avg 5 days overdue), 2 to Engineering (avg 3 days overdue), 2 to Marketing (avg 8 days overdue). Highest-risk item: 'API Documentation' (12 days overdue, blocking release). Draft email: 'Hi [PM Name], we have 7 overdue deliverables across three teams. Design and Marketing items are the oldest — recommend prioritizing API Documentation to unblock the release. Let me know if you need the full breakdown.' This synthesis combines list-item retrieval with AI reasoning to surface actionable insights.
This workflow chains a list-item query (requires Sites.Read.All) with the AI's summarization layer. The MCP fetches raw SharePoint data; the AI interprets priority and drafts prose. Accuracy depends on how consistently your team updates the Status column — stale metadata will produce misleading summaries.
Use-case deep-dives
When SharePoint MCP makes sense for HR onboarding flows
A 12-person startup runs new-hire onboarding through SharePoint lists—each row is a task, each column is an owner or due date. The SharePoint MCP lets your AI create the list item when a new employee starts, find the hiring manager in the directory, and drop the offer-letter PDF into a folder scoped to that cohort. The 6-tool surface is narrow but covers the CRUD loop HR needs. This works if your onboarding is already SharePoint-native and you're automating 2-5 hires a month. If you're stitching together Workday, Slack, and Google Drive, you'll spend more time mapping fields than you save. The buying call: your onboarding source-of-truth lives in SharePoint, and you want to skip the manual list-entry step.
Spinning up SharePoint folders when deals close
A 6-person consulting shop closes 3-4 new clients a quarter, and each client gets a SharePoint folder tree—kickoff docs, deliverables, invoices. The SharePoint MCP's folder-creation tool plugs into your CRM webhook: when a deal moves to "Closed Won" in HubSpot, the AI provisions the folder structure and drops a templated scope-of-work doc. OAuth2 auth means you grant it once per workspace, and the 6 tools cover folder and list setup without needing Graph API fluency. This breaks down if your folder taxonomy is deeply nested or if you need advanced permissions inheritance—the MCP doesn't expose fine-grained ACLs. The threshold: you're creating fewer than 20 folders a month, and your structure is 2-3 levels deep.
Logging resolved tickets into SharePoint lists for search
A 5-person support team closes 40 tickets a week in Zendesk, and the best resolutions should land in a SharePoint list so the whole company can search them. The SharePoint MCP's list-item tool writes a row—ticket ID, summary, resolution steps—after the AI summarizes the thread. The OAuth2 flow keeps it low-friction, and the list becomes a lightweight knowledge base without standing up a separate wiki. This works if your team already lives in SharePoint and you're capturing 10-15 entries a week. If you're over 100 tickets weekly, the list gets unwieldy and search degrades; you'd want a real knowledge platform. The call: SharePoint is your search hub, and you're automating the capture step for a modest ticket volume.
Frequently asked
What can the SharePoint MCP do in Switchy?
The SharePoint MCP lets your AI agents create folders, lists, and list items directly in your SharePoint sites. It can also manage users — adding them, finding them across Microsoft Graph and SharePoint, or removing them. Think of it as programmatic access to SharePoint's structure and user management, not document editing or search.
Do I need admin permissions to connect SharePoint?
Yes. The MCP uses OAuth2 and requires permissions to create lists, folders, and manage users via the SharePoint REST API. Your Microsoft 365 admin will need to approve the connection, or you'll need site owner rights at minimum. Standard SharePoint members can't grant these scopes.
Can the SharePoint MCP edit documents or search file contents?
No. It creates folders and list items, but doesn't read or write document contents. If you need AI to summarise Word docs or search PDFs in SharePoint, use the Microsoft Graph MCP or OneDrive MCP instead. This integration focuses on structure and metadata, not file bodies.
Why use this instead of SharePoint's web UI or Power Automate?
Use the MCP when your AI agents need to create SharePoint structure on the fly — like spinning up a project folder and list after analysing a Slack thread. Power Automate is better for scheduled or event-triggered workflows. The web UI is faster for one-off manual tasks.
Who on my team should connect the SharePoint MCP?
Whoever owns your SharePoint site architecture or has site collection admin rights. They'll authenticate once; then any Switchy workspace member can invoke the tools in their prompts. The connection doesn't count as a separate seat, but the OAuth token belongs to the person who connected it.