Microsoft 365 File Search MCP Server (SharePoint & OneDrive)

Created By
godwin3737a year ago
Overview

What is Microsoft 365 File Search MCP Server?

Microsoft 365 File Search MCP Server is a Model Context Protocol (MCP) server that provides advanced file search capabilities within Microsoft 365, specifically for SharePoint and OneDrive. It enables efficient file discovery and metadata analysis, integrating seamlessly with business workflows.

How to use Microsoft 365 File Search MCP Server?

To use the server, integrate it with Claude Desktop by updating the claude_desktop_config.json file with the necessary command and environment variables. You can perform file searches using the search_m365_files tool and retrieve file content using the get_file_content tool.

Key features of Microsoft 365 File Search MCP Server?

  • Advanced file search capabilities within Microsoft 365.
  • Metadata analysis for better file discovery.
  • Local caching of files to improve performance and reduce API calls.

Use cases of Microsoft 365 File Search MCP Server?

  1. Quickly finding documents in SharePoint or OneDrive.
  2. Analyzing file metadata for business insights.
  3. Integrating file search capabilities into business workflows.

FAQ from Microsoft 365 File Search MCP Server?

  • What is the purpose of the caching feature?

The caching feature improves performance by storing frequently accessed files locally, reducing the need for repeated API calls.

  • How do I perform a file search?

Use the search_m365_files tool with your search query to retrieve file metadata.

  • Can I retrieve the content of a specific file?

Yes, use the get_file_content tool with the appropriate drive ID and file ID to access the file content.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
godwin3737
Star
0
Language
Python
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)

a day ago